[html5] r3377 - [e] (0) Define the relationship of WebSocket to HTTP and TCP better.

[whatwg at whatwg.org]

Author: ianh
Date: 2009-07-08 00:00:50 -0700 (Wed, 08 Jul 2009)
New Revision: 3377

Modified:
   index
   source
Log:
[e] (0) Define the relationship of WebSocket to HTTP and TCP better.

Modified: index
===================================================================
--- index	2009-07-08 02:45:09 UTC (rev 3376)
+++ index	2009-07-08 07:00:50 UTC (rev 3377)
@@ -71223,6 +71223,7 @@
   Alan Plum,
   Alastair Campbell,
   Alex Nicolaou,
+  Alex Rousskov,
   Alexander J. Vincent,
   Alexey Feldgendler,
   Алексей Проскуряков (Alexey Proskuryakov),

Modified: source
===================================================================
--- source	2009-07-08 02:45:09 UTC (rev 3376)
+++ source	2009-07-08 07:00:50 UTC (rev 3377)
@@ -69295,6 +69295,7 @@
   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>
 
+
   <h6>Security model</h6>
 
   <p>The Web Socket protocol uses the origin model used by Web
@@ -69305,6 +69306,17 @@
   arbitrary origin string.</p>
 
 
+  <h6>Relationship to TCP/IP and HTTP</h6>
+
+  <p>WebSocket is an independent TCP-based protocol. It's only
+  relationship to HTTP is that its handshake is interpreted by HTTP
+  servers as an Upgrade request.</p>
+
+  <p>The WebSocket protocol by default uses port 81 for regular
+  WebSocket connections and port 815 for WebSocket connections
+  tunneled over TLS.</p>
+
+
   <!--BOILERPLATE middle-ietf-conformance-->
 
 
@@ -84012,6 +84024,7 @@
   Alan Plum,
   Alastair Campbell,
   Alex Nicolaou,
+  Alex Rousskov,
   Alexander J. Vincent,
   Alexey Feldgendler,
   Алексей Проскуряков (Alexey Proskuryakov),