[html5] r7173 - [e] (0) Fix some typos or copypasta. Fixing https://www.w3.org/Bugs/Public/show_ [...]

[whatwg at whatwg.org]

Author: ianh
Date: 2012-07-10 14:38:32 -0700 (Tue, 10 Jul 2012)
New Revision: 7173

Modified:
   complete.html
   index
   source
Log:
[e] (0) Fix some typos or copypasta.
Fixing https://www.w3.org/Bugs/Public/show_bug.cgi?id=17224
Affected topics: WebSocket API

Modified: complete.html
===================================================================
--- complete.html	2012-07-10 21:20:35 UTC (rev 7172)
+++ complete.html	2012-07-10 21:38:32 UTC (rev 7173)
@@ -83108,10 +83108,15 @@
   for example in an attempt to maintain local network NAT mappings, to
   detect failed connections, or to display latency metrics to the
   user. User agents must not use pings or unsolicited pongs to aid the
-  server; it is assumed that servers will send solicit pongs whenever
+  server; it is assumed that servers will solicit pongs whenever
   appropriate for the server's needs.</p>
 
+  <!-- v2: we'll probably add a way to make the client send pings and
+  automatically terminate the connection if they don't get a pong
+  within an author-provided timeout; see
+  https://www.w3.org/Bugs/Public/show_bug.cgi?id=17264 -->
 
+
   <h4 id=parsing-websocket-urls><span class=secno>10.3.5 </span>Parsing WebSocket URLs</h4>
 
   <p>The steps to <dfn id="parse-a-websocket-url's-components">parse a WebSocket URL's components</dfn> from

Modified: index
===================================================================
--- index	2012-07-10 21:20:35 UTC (rev 7172)
+++ index	2012-07-10 21:38:32 UTC (rev 7173)
@@ -83108,10 +83108,15 @@
   for example in an attempt to maintain local network NAT mappings, to
   detect failed connections, or to display latency metrics to the
   user. User agents must not use pings or unsolicited pongs to aid the
-  server; it is assumed that servers will send solicit pongs whenever
+  server; it is assumed that servers will solicit pongs whenever
   appropriate for the server's needs.</p>
 
+  <!-- v2: we'll probably add a way to make the client send pings and
+  automatically terminate the connection if they don't get a pong
+  within an author-provided timeout; see
+  https://www.w3.org/Bugs/Public/show_bug.cgi?id=17264 -->
 
+
   <h4 id=parsing-websocket-urls><span class=secno>10.3.5 </span>Parsing WebSocket URLs</h4>
 
   <p>The steps to <dfn id="parse-a-websocket-url's-components">parse a WebSocket URL's components</dfn> from

Modified: source
===================================================================
--- source	2012-07-10 21:20:35 UTC (rev 7172)
+++ source	2012-07-10 21:38:32 UTC (rev 7173)
@@ -96649,10 +96649,15 @@
   for example in an attempt to maintain local network NAT mappings, to
   detect failed connections, or to display latency metrics to the
   user. User agents must not use pings or unsolicited pongs to aid the
-  server; it is assumed that servers will send solicit pongs whenever
+  server; it is assumed that servers will solicit pongs whenever
   appropriate for the server's needs.</p>
 
+  <!-- v2: we'll probably add a way to make the client send pings and
+  automatically terminate the connection if they don't get a pong
+  within an author-provided timeout; see
+  https://www.w3.org/Bugs/Public/show_bug.cgi?id=17264 -->
 
+
   <h4>Parsing WebSocket URLs</h4>
 
   <p>The steps to <dfn>parse a WebSocket URL's components</dfn> from