html5/websockets Overview.html,1.232,1.233

Update of /sources/public/html5/websockets
In directory hutz:/tmp/cvs-serv21097

Modified Files:
	Overview.html 
Log Message:
Make the client-side failure mode also fire 'error'. (whatwg r6377)

Index: Overview.html
===================================================================
RCS file: /sources/public/html5/websockets/Overview.html,v
retrieving revision 1.232
retrieving revision 1.233
diff -u -d -r1.232 -r1.233
--- Overview.html	28 Jul 2011 01:29:23 -0000	1.232
+++ Overview.html	5 Aug 2011 23:34:55 -0000	1.233
@@ -213,7 +213,7 @@
 
    <h1>The WebSocket API</h1>
    
-   <h2 class="no-num no-toc" id="editor-s-draft-28-july-2011">Editor's Draft 28 July 2011</h2>
+   <h2 class="no-num no-toc" id="editor-s-draft-5-august-2011">Editor's Draft 5 August 2011</h2>
    <dl><dt>Latest Published Version:</dt>
     <dd><a href="http://www.w3.org/TR/websockets/">http://www.w3.org/TR/websockets/</a></dd>
     <dt>Latest Editor's Draft:</dt>
@@ -317,7 +317,7 @@
   </dl><p>The W3C <a href="http://www.w3.org/2008/webapps/">Web Applications
   Working Group</a> is the W3C working group responsible for this
   specification's progress along the W3C Recommendation track.
-  This specification is the 28 July 2011 Editor's Draft.
+  This specification is the 5 August 2011 Editor's Draft.
   <p>This specification is being developed in conjunction with an
   Internet Draft for a wire protocol, the WebSocket Protocol,
   available from the following location:<ul><li>WebSocket Protocol Internet-Draft: <a href="http://www.whatwg.org/specs/web-socket-protocol/">http://www.whatwg.org/specs/web-socket-protocol/</a></li>
@@ -715,16 +715,16 @@
 
     <p>If the <var title="">data</var> argument has any unpaired
     surrogates, then raise an <code>SYNTAX_ERR</code> exception. If
-    <i>the WebSocket connection is established</i>, and the
-    string has no unpaired surrogates, and <i title="the WebSocket
-    closing handshake is started">the WebSocket closing handshake has
-    not yet started</i>, then the user agent must <i>send a WebSocket
+    <i>the WebSocket connection is established</i>, and the string has
+    no unpaired surrogates, and <i title="the WebSocket closing
+    handshake is started">the WebSocket closing handshake has not yet
+    started</i>, then the user agent must <i>send a WebSocket
     Message</i> comprised of <var title="">data</var> using a text
     frame opcode; if the data cannot be sent, e.g. because it would
     need to be buffered but the buffer is full, the user agent must
-    <i>close the WebSocket connection</i>. Any invokation of this
-    method with a string argument that does not raise an exception
-    must increase the <code title="dom-WebSocket-bufferedAmount"><a href="#dom-websocket-bufferedamount">bufferedAmount</a></code>
+    <i>close the WebSocket connection</i> <a href="#concept-websocket-close-fail" title="concept-websocket-close-fail">with prejudice</a>. Any
+    invokation of this method with a string argument that does not
+    raise an exception must increase the <code title="dom-WebSocket-bufferedAmount"><a href="#dom-websocket-bufferedamount">bufferedAmount</a></code>
     attribute by the number of bytes needed to express the argument as
     UTF-8. <a href="#refsRFC3629">[RFC3629]</a> <a href="#refsWSP">[WSP]</a></p>
 
@@ -740,8 +740,9 @@
     must <i>send a WebSocket Message</i> comprised of <var title="">data</var> using a binary frame opcode; if the data
     cannot be sent, e.g. because it would need to be buffered but the
     buffer is full, the user agent must <i>close the WebSocket
-    connection</i>. The data to be sent is the raw data represented by
-    the <code>Blob</code> object.  Any
+    connection</i> <a href="#concept-websocket-close-fail" title="concept-websocket-close-fail">with
+    prejudice</a>. The data to be sent is the raw data represented
+    by the <code>Blob</code> object.  Any
     invokation of this method with a <code>Blob</code> argument that
     does not raise an exception must increase the <code title="dom-WebSocket-bufferedAmount"><a href="#dom-websocket-bufferedamount">bufferedAmount</a></code>
     attribute by the size of the <code>Blob</code> object's raw data,
@@ -759,7 +760,8 @@
     must <i>send a WebSocket Message</i> comprised of <var title="">data</var> using a binary frame opcode; if the data
     cannot be sent, e.g. because it would need to be buffered but the
     buffer is full, the user agent must <i>close the WebSocket
-    connection</i>. The data to be sent is the data stored in the
+    connection</i> <a href="#concept-websocket-close-fail" title="concept-websocket-close-fail">with
+    prejudice</a>. The data to be sent is the data stored in the
     buffer described by the <code>ArrayBuffer</code> object.  Any invokation of this method with an
     <code>ArrayBuffer</code> argument that does not raise an exception
     must increase the <code title="dom-WebSocket-bufferedAmount"><a href="#dom-websocket-bufferedamount">bufferedAmount</a></code>
@@ -850,14 +852,16 @@
   <code title="dom-WebSocket-close"><a href="#dom-websocket-close">close()</a></code> method was called,
   the <code title="dom-WebSocket-readyState"><a href="#dom-websocket-readystate">readyState</a></code>
   attribute's value will already be set to <code title="dom-WebSocket-CLOSING"><a href="#dom-websocket-closing">CLOSING</a></code> (2) when this task
-  runs.) <a href="#refsWSP">[WSP]</a><p id="closeWebSocket">When <i>the WebSocket connection is
+  runs.) <a href="#refsWSP">[WSP]</a><hr><p id="closeWebSocket">When <i>the WebSocket connection is
   closed</i>, possibly <i title="">cleanly</i>, the user agent must
   <span>queue a task</span> to run the following substeps:<ol><li><p>Change the <code title="dom-WebSocket-readyState"><a href="#dom-websocket-readystate">readyState</a></code> attribute's
    value to <code title="dom-WebSocket-CLOSED"><a href="#dom-websocket-closed">CLOSED</a></code>
    (3).</li>
 
    <li><p>If the user agent was required to <i>fail the websocket
-   connection</i>, <span>fire a simple event</span> named <code title="">error</code> at the <code><a href="#websocket">WebSocket</a></code> object. <a href="#refsWSP">[WSP]</a></li>
+   connection</i> or <i>the WebSocket connection is closed</i> <dfn id="concept-websocket-close-fail" title="concept-websocket-close-fail">with prejudice</dfn>,
+   <span>fire a simple event</span> named <code title="">error</code>
+   at the <code><a href="#websocket">WebSocket</a></code> object. <a href="#refsWSP">[WSP]</a></li>
 
    <li><p>Create an event that uses the <code><a href="#closeevent">CloseEvent</a></code>
    interface, with the event name <code title="event-close">close</code>, which does not bubble, is not

Received on Friday, 5 August 2011 23:35:06 UTC