[html5] r5242 - [giow] (1) Make WebSocket.send() return void.

[whatwg at whatwg.org]

Author: ianh
Date: 2010-08-05 18:01:43 -0700 (Thu, 05 Aug 2010)
New Revision: 5242

Modified:
   complete.html
   source
Log:
[giow] (1) Make WebSocket.send() return void.

Modified: complete.html
===================================================================
--- complete.html	2010-08-06 00:38:10 UTC (rev 5241)
+++ complete.html	2010-08-06 01:01:43 UTC (rev 5242)
@@ -72352,7 +72352,7 @@
            attribute <a href=#function>Function</a> <a href=#handler-websocket-onerror title=handler-WebSocket-onerror>onerror</a>;
            attribute <a href=#function>Function</a> <a href=#handler-websocket-onclose title=handler-WebSocket-onclose>onclose</a>;
   readonly attribute DOMString <a href=#dom-websocket-protocol title=dom-WebSocket-protocol>protocol</a>;
-  boolean <a href=#dom-websocket-send title=dom-WebSocket-send>send</a>(in DOMString data);
+  void <a href=#dom-websocket-send title=dom-WebSocket-send>send</a>(in DOMString data);
   void <a href=#dom-websocket-close title=dom-WebSocket-close>close</a>();
 };
 <a href=#websocket>WebSocket</a> implements <a href=#eventtarget>EventTarget</a>;</pre>
@@ -72485,15 +72485,12 @@
   it must raise <code><a href=#syntax_err>SYNTAX_ERR</a></code>. If the connection is
   established, and the string has no unpaired surrogates, and <a href=#the-websocket-closing-handshake-has-started title="the WebSocket closing handshake has started">the WebSocket
   closing handshake has not yet started</a>, then the user agent
-  must <a href=#send-data-using-the-websocket>send <var title="">data</var> using the
-  WebSocket</a>. If the data cannot be sent, e.g. because it would
-  need to be buffered but the buffer is full, the user agent must
-  <a href=#close-the-websocket-connection>close the WebSocket connection</a>. The method must then
-  return true if the connection is still established (and the data was
-  queued or sent successfully), or false if the connection is closing
-  or closed (e.g. because the user agent just had a buffer overflow
-  and failed to send the data, or because <a href=#the-websocket-closing-handshake-has-started>the WebSocket closing
-  handshake has started</a>).</p>
+  must <a href=#send-data-using-the-websocket>send <var title="">data</var> using the WebSocket</a>;
+  if the data cannot be sent, e.g. because it would need to be
+  buffered but the buffer is full, the user agent must <a href=#close-the-websocket-connection>close the
+  WebSocket connection</a>. Any invokation of this method 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.</p>
 
   <p>The <dfn id=dom-websocket-close title=dom-WebSocket-close><code>close()</code></dfn>
   method must run the first matching steps from the following list:</p>

Modified: source
===================================================================
--- source	2010-08-06 00:38:10 UTC (rev 5241)
+++ source	2010-08-06 01:01:43 UTC (rev 5242)
@@ -81368,7 +81368,7 @@
            attribute <span>Function</span> <span title="handler-WebSocket-onerror">onerror</span>;
            attribute <span>Function</span> <span title="handler-WebSocket-onclose">onclose</span>;
   readonly attribute DOMString <span title="dom-WebSocket-protocol">protocol</span>;
-  boolean <span title="dom-WebSocket-send">send</span>(in DOMString data);
+  void <span title="dom-WebSocket-send">send</span>(in DOMString data);
   void <span title="dom-WebSocket-close">close</span>();
 };
 <span>WebSocket</span> implements <span>EventTarget</span>;</pre>
@@ -81532,15 +81532,13 @@
   established, and the string has no unpaired surrogates, and <span
   title="the WebSocket closing handshake has started">the WebSocket
   closing handshake has not yet started</span>, then the user agent
-  must <span>send <var title="">data</var> using the
-  WebSocket</span>. If the data cannot be sent, e.g. because it would
-  need to be buffered but the buffer is full, the user agent must
-  <span>close the WebSocket connection</span>. The method must then
-  return true if the connection is still established (and the data was
-  queued or sent successfully), or false if the connection is closing
-  or closed (e.g. because the user agent just had a buffer overflow
-  and failed to send the data, or because <span>the WebSocket closing
-  handshake has started</span>).</p>
+  must <span>send <var title="">data</var> using the WebSocket</span>;
+  if the data cannot be sent, e.g. because it would need to be
+  buffered but the buffer is full, the user agent must <span>close the
+  WebSocket connection</span>. Any invokation of this method that does
+  not raise an exception must increase the <code
+  title="dom-WebSocket-bufferedAmount">bufferedAmount</code> attribute
+  by the number of bytes needed to express the argument as UTF-8.</p>
 
   <p>The <dfn title="dom-WebSocket-close"><code>close()</code></dfn>
   method must run the first matching steps from the following list:</p>