websockets; hixie: Define whether amountBuffered includes overhead or not (it does not). (whatwg r4812)

websockets; hixie: Define whether amountBuffered includes overhead or
not (it does not). (whatwg r4812)

http://dev.w3.org/cvsweb/html5/websockets/Overview.html?r1=1.156&r2=1.157&f=h
http://html5.org/tools/web-apps-tracker?from=4811&to=4812

===================================================================
RCS file: /sources/public/html5/websockets/Overview.html,v
retrieving revision 1.156
retrieving revision 1.157
diff -u -d -r1.156 -r1.157
--- Overview.html 22 Feb 2010 23:03:41 -0000 1.156
+++ Overview.html 25 Feb 2010 09:23:42 -0000 1.157
@@ -193,7 +193,7 @@
    <p><a href="http://www.w3.org/"><img alt="W3C" height="48" src="http://www.w3.org/Icons/w3c_home" width="72"></a></p>
    <h1>The Web Sockets API</h1>
 
-   <h2 class="no-num no-toc" id="editor-s-draft-22-february-2010">Editor's Draft 22 February 2010</h2>
+   <h2 class="no-num no-toc" id="editor-s-draft-25-february-2010">Editor's Draft 25 February 2010</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>
@@ -257,7 +257,7 @@
   Working Group</a> is the W3C working group responsible for this
   specification's progress along the W3C Recommendation track.
 
-  This specification is the 22 February 2010 Editor's Draft.
+  This specification is the 25 February 2010 Editor's Draft.
   <p>This specification is being developed in conjunction with an
   Internet Draft for a wire protocol, the Web Socket Protocol,
   available from the IETF at the following location:<ul><li>WebSocket Protocol Internet-Draft: <a href="http://tools.ietf.org/html/draft-hixie-thewebsocketprotocol">http://tools.ietf.org/html/draft-hixie-thewebsocketprotocol</a></li>
@@ -456,8 +456,9 @@
   be queued to fire a <code title="event-close">close</code> event, as
   <a href="#closeWebSocket">described below</a>.<hr><p>The <dfn id="dom-websocket-bufferedamount" title="dom-WebSocket-bufferedAmount"><code>bufferedAmount</code></dfn>
   attribute must return the number of bytes that have been queued but
-  not yet sent. If the connection is closed, this attribute's value
-  will only increase with each call to the <code title="dom-WebSocket-send"><a href="#dom-websocket-send">send()</a></code> method (the number does not
+  not yet sent. This does not include framing overhead incurred by the
+  protocol. If the connection is closed, this attribute's value will
+  only increase with each call to the <code title="dom-WebSocket-send"><a href="#dom-websocket-send">send()</a></code> method (the number does not
   reset to zero once the connection closes).<div class="example">
 
    <p>In this simple example, the <code title="dom-WebSocket-bufferedAmount"><a href="#dom-websocket-bufferedamount">bufferedAmount</a></code>

Received on Thursday, 25 February 2010 09:24:21 UTC