- From: CVS User ihickson <cvsmail@w3.org>
- Date: Tue, 19 Nov 2013 21:15:42 +0000
- To: public-html-commits@w3.org
Update of /sources/public/html5/websockets
In directory roscoe:/tmp/cvs-serv24031
Modified Files:
Overview.html
Log Message:
Reword the concept of closing a WebSocket with prejudice so that it's more obviously a flag (whatwg r8298)
--- /sources/public/html5/websockets/Overview.html 2013/11/08 23:21:12 1.303
+++ /sources/public/html5/websockets/Overview.html 2013/11/19 21:15:42 1.304
@@ -216,7 +216,7 @@
<h1>The WebSocket API</h1>
- <h2 class="no-num no-toc" id="editor-s-draft-8-november-2013">Editor's Draft 8 November 2013</h2>
+ <h2 class="no-num no-toc" id="editor-s-draft-19-november-2013">Editor's Draft 19 November 2013</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>
@@ -350,7 +350,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 8 November 2013 Editor's Draft.
+ This specification is the 19 November 2013 Editor's Draft.
</p>
@@ -786,6 +786,7 @@
string "<code title="">blob</code>". On getting, it must return the last value it was set to. On
setting, the user agent must set the IDL attribute to the new value.</p>
+
<p class="note">This attribute allows authors to control how binary data is exposed to scripts. By
setting the attribute to "<code title="">blob</code>", binary data is returned in
<code>Blob</code> form; by setting it to "<code title="">arraybuffer</code>", it is returned in
@@ -807,13 +808,15 @@
<dd>
+
<p>Let <var title="">data</var> be the result of <span title="convert a DOMString to a sequence
of Unicode characters">converting the <var title="">data</var> argument to a sequence of Unicode
characters</span>. If <i>the WebSocket connection is established</i> 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> <a href="#concept-websocket-close-fail" title="concept-websocket-close-fail">with prejudice</a>. Any invocation of this method with a
+ buffer is full, the user agent must <a href="#concept-websocket-close-fail" title="concept-websocket-close-fail">flag the WebSocket
+ as full</a> and then <i>close the WebSocket connection</i>. Any invocation of this method with a
string argument that does not throw 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="#refsUNICODE">[UNICODE]</a> <a href="#refsRFC3629">[RFC3629]</a> <a href="#refsWSP">[WSP]</a></p>
@@ -824,11 +827,13 @@
<dd>
+
<p>If <i>the WebSocket connection is established</i>, 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 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> <a href="#concept-websocket-close-fail" title="concept-websocket-close-fail">with prejudice</a>. The data to be sent is the raw data
+ buffer is full, the user agent must <a href="#concept-websocket-close-fail" title="concept-websocket-close-fail">flag the WebSocket
+ as full</a> and then <i>close the WebSocket connection</i>. The data to be sent is the raw data
represented by the <code>Blob</code> object. Any invocation of this method with a
<code>Blob</code> argument that does not throw 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, in bytes. <a href="#refsWSP">[WSP]</a> <a href="#refsFILEAPI">[FILEAPI]</a></p>
@@ -840,11 +845,13 @@
<dd>
+
<p>If <i>the WebSocket connection is established</i>, 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 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> <a href="#concept-websocket-close-fail" title="concept-websocket-close-fail">with prejudice</a>. The data to be sent is the data
+ buffer is full, the user agent must <a href="#concept-websocket-close-fail" title="concept-websocket-close-fail">flag the WebSocket
+ as full</a> and then <i>close the WebSocket connection</i>. The data to be sent is the data
stored in the buffer described by the <code>ArrayBuffer</code> object.
Any invocation of this method with an <code>ArrayBuffer</code> argument that does not throw an
exception must increase the <code title="dom-WebSocket-bufferedAmount"><a href="#dom-websocket-bufferedamount">bufferedAmount</a></code>
@@ -857,11 +864,13 @@
<dd>
+
<p>If <i>the WebSocket connection is established</i>, 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 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> <a href="#concept-websocket-close-fail" title="concept-websocket-close-fail">with prejudice</a>. The data to be sent is the data
+ buffer is full, the user agent must <a href="#concept-websocket-close-fail" title="concept-websocket-close-fail">flag the WebSocket
+ as full</a> and then <i>close the WebSocket connection</i>. The data to be sent is the data
stored in the section of the buffer described by the <code>ArrayBuffer</code> object that the
<code>ArrayBufferView</code> object references. Any invocation of
this method with an <code>ArrayBufferView</code> argument that does not throw an exception must
@@ -986,8 +995,9 @@
<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> or <i>the WebSocket
- connection is closed</i> <dfn id="concept-websocket-close-fail" title="concept-websocket-close-fail">with prejudice</dfn>,
+
+ <li><p>If the user agent was required to <i>fail the WebSocket connection</i>, or if the <i title="the WebSocket connection is closed">the WebSocket connection was closed</i> after being
+ <dfn id="concept-websocket-close-fail" title="concept-websocket-close-fail">flagged as full</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>
Received on Tuesday, 19 November 2013 21:15:44 UTC