[html5] r3278 - [e] (0) websocket protocol intro (part 1)

whatwg at whatwg.org whatwg at whatwg.org
Tue Jun 16 10:43:14 PDT 2009

Author: ianh
Date: 2009-06-16 10:43:13 -0700 (Tue, 16 Jun 2009)
New Revision: 3278

[e] (0) websocket protocol intro (part 1)

Modified: source
--- source	2009-06-16 01:59:29 UTC (rev 3277)
+++ source	2009-06-16 17:43:13 UTC (rev 3278)
@@ -69155,9 +69155,27 @@
-  <p class="XXX">...</p>
+  <p>The WebSocket protocol is designed on the principle that there
+  should be minimal framing (the only framing that exists is to make
+  the protocol frame-based instead of stream-based, and to support a
+  distinction between Unicode text and binary frames). It is expected
+  that metadata would be layered on top of WebSocket by the
+  application layer, in the same way that metadata is layered on top
+  of TCP/IP by the application layer (HTTP).</p>
+  <p>Conceptually, WebSocket is really just a layer on top of TCP/IP
+  that adds a Web "origin"-based security model for browsers; adds an
+  addressing and protocol naming mechanism to support multiple
+  services on one port and multiple host names on one IP address; and
+  layers a framing mechanism on top of TCP to get back to the IP
+  packet mechanism that TCP is built on, but without length
+  limits. Other than that, it adds nothing. Basically it is intended
+  to be as close as possible to just exposing raw TCP/IP to script as
+  possible given the constraints of the Web. It's also designed in
+  such a way that its servers can share a port with HTTP servers, by
+  having its handshake be a valid HTTP Upgrade handshake also.</p>
   <!--BOILERPLATE middle-ietf-conformance-->

More information about the Commit-Watchers mailing list