[html5] r4268 - [e] (0) Change the WebSocket spec to not claim that using port 80 is simple, jus [...]

[whatwg at whatwg.org]

Author: ianh
Date: 2009-10-21 16:46:01 -0700 (Wed, 21 Oct 2009)
New Revision: 4268

Modified:
   complete.html
   source
Log:
[e] (0) Change the WebSocket spec to not claim that using port 80 is simple, just that it seems that way.

Modified: complete.html
===================================================================
--- complete.html	2009-10-21 12:26:55 UTC (rev 4267)
+++ complete.html	2009-10-21 23:46:01 UTC (rev 4268)
@@ -66458,15 +66458,15 @@
 
   <p>There are several options for establishing a Web Socket connection.</p>
 
-  <p>The simplest method is to use port 80 to get a direct connection
-  to a Web Socket server. Port 80 traffic, however, will often be
-  intercepted by HTTP proxies, which can lead to the connection
-  failing to be established.</p>
+  <p>On the face of it, the simplest method would seem to be to use
+  port 80 to get a direct connection to a Web Socket server. Port 80
+  traffic, however, will often be intercepted by HTTP proxies, which
+  can lead to the connection failing to be established.</p>
 
-  <p>The second simplest method is to use TLS encryption and port 443
-  to connect directly to a Web Socket server. This has the advantage
-  of being more secure; however, TLS encryption can be computationally
-  expensive.</p>
+  <p>The most reliable method, therefore, is to use TLS encryption and
+  port 443 to connect directly to a Web Socket server. This has the
+  advantage of being more secure; however, TLS encryption can be
+  computationally expensive.</p>
 
   <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

Modified: source
===================================================================
--- source	2009-10-21 12:26:55 UTC (rev 4267)
+++ source	2009-10-21 23:46:01 UTC (rev 4268)
@@ -74646,15 +74646,15 @@
 
   <p>There are several options for establishing a Web Socket connection.</p>
 
-  <p>The simplest method is to use port 80 to get a direct connection
-  to a Web Socket server. Port 80 traffic, however, will often be
-  intercepted by HTTP proxies, which can lead to the connection
-  failing to be established.</p>
+  <p>On the face of it, the simplest method would seem to be to use
+  port 80 to get a direct connection to a Web Socket server. Port 80
+  traffic, however, will often be intercepted by HTTP proxies, which
+  can lead to the connection failing to be established.</p>
 
-  <p>The second simplest method is to use TLS encryption and port 443
-  to connect directly to a Web Socket server. This has the advantage
-  of being more secure; however, TLS encryption can be computationally
-  expensive.</p>
+  <p>The most reliable method, therefore, is to use TLS encryption and
+  port 443 to connect directly to a Web Socket server. This has the
+  advantage of being more secure; however, TLS encryption can be
+  computationally expensive.</p>
 
   <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