[html5] r3437 - [e] (0) Elaborate on when you might share ports.

whatwg at whatwg.org whatwg at whatwg.org
Thu Jul 16 20:27:13 PDT 2009


Author: ianh
Date: 2009-07-16 20:27:12 -0700 (Thu, 16 Jul 2009)
New Revision: 3437

Modified:
   source
Log:
[e] (0) Elaborate on when you might share ports.

Modified: source
===================================================================
--- source	2009-07-17 01:30:41 UTC (rev 3436)
+++ source	2009-07-17 03:27:12 UTC (rev 3437)
@@ -69705,9 +69705,16 @@
   <p>When a connection is to be made to a port that is shared by an
   HTTP server (a situation that is quite likely to occur with traffic
   to ports 80 and 443), the connection will appear to the HTTP server
-  to be a regular GET request with an Upgrade offer.</p>
+  to be a regular GET request with an Upgrade offer. In relatively
+  simple setups with just one IP address and a single server for all
+  traffic to a single hostname, this might allow a practical way for
+  systems based on the Web Socket protocol to be deployed. In more
+  elaborate setups (e.g. with load balancers and multiple servers), a
+  dedicated set of hosts for Web Socket connections separate from the
+  HTTP servers is probably easier to manage.</p>
 
 
+
   <!--BOILERPLATE middle-ietf-conformance-->
 
 




More information about the Commit-Watchers mailing list