- From: Ian Hickson via cvs-syncmail <cvsmail@w3.org>
- Date: Wed, 27 Jul 2011 20:37:38 +0000
- To: public-html-commits@w3.org
Update of /sources/public/html5/websockets In directory hutz:/tmp/cvs-serv25865 Modified Files: Overview.html Log Message: WebSocket: Disallow this controversial extension rather than require it. (whatwg r6330) Index: Overview.html =================================================================== RCS file: /sources/public/html5/websockets/Overview.html,v retrieving revision 1.230 retrieving revision 1.231 diff -u -d -r1.230 -r1.231 --- Overview.html 19 Jul 2011 21:40:04 -0000 1.230 +++ Overview.html 27 Jul 2011 20:37:36 -0000 1.231 @@ -211,7 +211,7 @@ <h1>The WebSocket API</h1> - <h2 class="no-num no-toc" id="editor-s-draft-19-july-2011">Editor's Draft 19 July 2011</h2> + <h2 class="no-num no-toc" id="editor-s-draft-27-july-2011">Editor's Draft 27 July 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> @@ -315,7 +315,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 19 July 2011 Editor's Draft. + This specification is the 27 July 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> @@ -494,13 +494,12 @@ <li> <p><i>Establish a WebSocket connection</i> given the set (<var title="">host</var>, <var title="">port</var>, <var title="">resource name</var>, <var title="">secure</var>), along - with the <var title="">protocols</var> list, a list containing - just "<code title="">deflate-stream</code>" for the extensions, - and <var title="">origin</var>. The <i>headers to send appropriate - cookies</i> must be a <code title="http-Cookie">Cookie</code> - header whose value is the <i>cookie-string</i> computed from the - user's cookie store and the URL <var title="">url</var>; for these - purposes this is <em>not</em> a "non-HTTP" API. <a href="#refsWSP">[WSP]</a> <a href="#refsCOOKIES">[COOKIES]</a></p> + with the <var title="">protocols</var> list, an empty list for the + extensions, and <var title="">origin</var>. The <i>headers to send + appropriate cookies</i> must be a <code title="http-Cookie">Cookie</code> header whose value is the + <i>cookie-string</i> computed from the user's cookie store and the + URL <var title="">url</var>; for these purposes this is + <em>not</em> a "non-HTTP" API. <a href="#refsWSP">[WSP]</a> <a href="#refsCOOKIES">[COOKIES]</a></p> <p>When the user agent <i title="validate the server's response">validates the server's response</i> during the @@ -555,8 +554,7 @@ WebSocket connection is established</i>, its value might change, as defined below.<p class="note">The <code title="dom-WebSocket-extensions"><a href="#dom-websocket-extensions">extensions</a></code> attribute returns the extensions selected by the server, if any. (Currently this will - only ever be either the empty string or "deflate-stream", the latter - indicating that the data is being compressed.)<p>The <dfn id="dom-websocket-protocol" title="dom-WebSocket-protocol"><code>protocol</code></dfn> attribute + only ever be the empty string.)<p>The <dfn id="dom-websocket-protocol" title="dom-WebSocket-protocol"><code>protocol</code></dfn> attribute must initially return the empty string. After <i>the WebSocket connection is established</i>, its value might change, as defined below.<p class="note">The <code title="dom-WebSocket-protocol"><a href="#dom-websocket-protocol">protocol</a></code> attribute returns the
Received on Wednesday, 27 July 2011 20:37:40 UTC