[html5] r4129 - [e] (0) Update the WS abstract.

[whatwg at whatwg.org]

Author: ianh
Date: 2009-10-13 16:23:13 -0700 (Tue, 13 Oct 2009)
New Revision: 4129

Modified:
   complete.html
   source
Log:
[e] (0) Update the WS abstract.

Modified: complete.html
===================================================================
--- complete.html	2009-10-13 21:42:56 UTC (rev 4128)
+++ complete.html	2009-10-13 23:23:13 UTC (rev 4129)
@@ -956,11 +956,16 @@
      <li><a href=#feedback-from-the-protocol><span class=secno>10.3.3 </span>Feedback from the protocol</a>
       <ol>
        <li><a href=#garbage-collection-1><span class=secno>10.3.3.1 </span>Garbage collection</a></ol></li>
-     <li><a href=#websocket-protocol title="This protocol enables two-way
-  communication between a user agent running untrusted code running in
-  a controlled environment to a remote host that understands the
-  protocol. It is designed to be easy to implement on the server
-  side."><span class=secno>10.3.4 </span>The Web Socket protocol</a>
+     <li><a href=#websocket-protocol title="The Web Sockets protocol enables
+  two-way communication between a user agent running untrusted code
+  running in a controlled environment to a remote host that has
+  opted-in to communications from that code. The protocol consists of
+  an initial handshake followed by basic message framing, layered over
+  TCP. The goal of this technology is to provide a mechanism for
+  browser-based applications that need two-way communication with
+  servers that does not rely on opening multiple HTTP connections
+  (e.g. using XMLHttpRequest or <iframe>s and long
+  polling)."><span class=secno>10.3.4 </span>The Web Socket protocol</a>
       <ol>
        <li><a href=#introduction-8><span class=secno>10.3.4.1 </span>Introduction</a>
         <ol>
@@ -65865,11 +65870,16 @@
 
   
 
-  <h4 id=websocket-protocol title="This protocol enables two-way
-  communication between a user agent running untrusted code running in
-  a controlled environment to a remote host that understands the
-  protocol. It is designed to be easy to implement on the server
-  side."><span class=secno>10.3.4 </span>The Web Socket protocol</h4>
+  <h4 id=websocket-protocol title="The Web Sockets protocol enables
+  two-way communication between a user agent running untrusted code
+  running in a controlled environment to a remote host that has
+  opted-in to communications from that code. The protocol consists of
+  an initial handshake followed by basic message framing, layered over
+  TCP. The goal of this technology is to provide a mechanism for
+  browser-based applications that need two-way communication with
+  servers that does not rely on opening multiple HTTP connections
+  (e.g. using XMLHttpRequest or <iframe>s and long
+  polling)."><span class=secno>10.3.4 </span>The Web Socket protocol</h4>
 
   <div class=no-rfc>
    <p class=note>This section will be extracted into an RFC in due

Modified: source
===================================================================
--- source	2009-10-13 21:42:56 UTC (rev 4128)
+++ source	2009-10-13 23:23:13 UTC (rev 4129)
@@ -74068,11 +74068,16 @@
 
   <!--START websocket-protocol-->
 
-  <h4 id="websocket-protocol" title="This protocol enables two-way
-  communication between a user agent running untrusted code running in
-  a controlled environment to a remote host that understands the
-  protocol. It is designed to be easy to implement on the server
-  side.">The Web Socket protocol</h4>
+  <h4 id="websocket-protocol" title="The Web Sockets protocol enables
+  two-way communication between a user agent running untrusted code
+  running in a controlled environment to a remote host that has
+  opted-in to communications from that code. The protocol consists of
+  an initial handshake followed by basic message framing, layered over
+  TCP. The goal of this technology is to provide a mechanism for
+  browser-based applications that need two-way communication with
+  servers that does not rely on opening multiple HTTP connections
+  (e.g. using XMLHttpRequest or <iframe>s and long
+  polling).">The Web Socket protocol</h4>
 
   <div class="no-rfc">
    <p class="note">This section will be extracted into an RFC in due