W3C home > Mailing lists > Public > whatwg@whatwg.org > March 2011

[whatwg] whatwg Digest, Vol 84, Issue 74

From: Bob Gezelter <gezelter@rlgsc.com>
Date: Thu, 31 Mar 2011 07:51:01 -0500
Message-ID: <4D9478B5.3070503@rlgsc.com>
Jonathan,

The WebSocket protocol currently presumes TCP as the underlying transport.

TCP connections are an uninterrupted stream. If a packet is lost, the
connection will be aborted.

I do not believe that the TCP dependency is truly necessary or beneficial.
WADR, it would be far more appropriate to specify the needed characteristics
of the underlying transport. As an example, the earliest versions of MTP
(RFC 772) -- the predecessor of SMTP have successfully taken this approach
to specification.

In a recent posting to my blog, Ruminations, I suggested that the WebSocket
protocol specification be segregated into multiple RFCs, to separate the
TCP-related implementation issues from the underlying protocol.

- Bob
+--------------------------------------------------------------------------+
| Robert "Bob" Gezelter                       E-Mail:  gezelter at rlgsc.com  |
| Robert Gezelter Software Consultant                                      |
| 35-20 167th Street, Suite 215               Fax:       (on Request)      |
| Flushing, New York  11358-1731                                           |
| United States of America                    http://www.rlgsc.com         |
+--------------------------------------------------------------------------+
Received on Thursday, 31 March 2011 05:51:01 UTC

This archive was generated by hypermail 2.4.0 : Wednesday, 22 January 2020 16:59:31 UTC