Skip to content

Commit

Permalink
Browse files Browse the repository at this point in the history
[e] (0) Minor editorial tweaks for WebSocket.
git-svn-id: http://svn.whatwg.org/webapps@2637 340c8d12-0b0e-0410-8428-c7bf67bfef74
  • Loading branch information
Hixie committed Jan 8, 2009
1 parent 969644f commit 7a01ab4
Show file tree
Hide file tree
Showing 2 changed files with 18 additions and 16 deletions.
19 changes: 10 additions & 9 deletions index
Expand Up @@ -21,7 +21,7 @@
<div class=head>
<p><a class=logo href=http://www.whatwg.org/ rel=home><img alt=WHATWG src=/images/logo></a></p>
<h1>HTML 5</h1>
<h2 class="no-num no-toc" id=draft-recommendation-&mdash;-date:-01-jan-1901>Draft Recommendation &mdash; 6 January 2009</h2>
<h2 class="no-num no-toc" id=draft-recommendation-&mdash;-date:-01-jan-1901>Draft Recommendation &mdash; 8 January 2009</h2>
<p>You can take part in this work. <a href=http://www.whatwg.org/mailing-list>Join the working group's discussion list.</a></p>
<p><strong>Web designers!</strong> We have a <a href=http://blog.whatwg.org/faq/>FAQ</a>, a <a href=http://forums.whatwg.org/>forum</a>, and a <a href=http://www.whatwg.org/mailing-list#help>help mailing list</a> for you!</p>
<dl><dt>Multiple-page version:</dt>
Expand Down Expand Up @@ -851,7 +851,7 @@
<li><a href=#network-intro><span class=secno>7.3.1 </span>Introduction</a></li>
<li><a href=#the-websocket-interface><span class=secno>7.3.2 </span>The <code>WebSocket</code> interface</a></li>
<li><a href=#websocket-events><span class=secno>7.3.3 </span>WebSocket Events</a></li>
<li><a href=#the-web-socket-protocol><span class=secno>7.3.4 </span>The Web Socket protocol</a>
<li><a href=#websocket-protocol><span class=secno>7.3.4 </span>The Web Socket protocol</a>
<ol>
<li><a href=#client-side-requirements><span class=secno>7.3.4.1 </span>Client-side requirements</a>
<ol>
Expand Down Expand Up @@ -44180,15 +44180,16 @@ interface <dfn id=websocket>WebSocket</dfn> {
<dd><p>Must be invoked whenever an <code title=event-WebSocket-closed>closed</code> event is targeted at or
bubbles through the <code><a href=#websocket>WebSocket</a></code> object.</dd>

</dl><h4 id=the-web-socket-protocol><span class=secno>7.3.4 </span>The Web Socket protocol</h4>
</dl><h4 id=websocket-protocol><span class=secno>7.3.4 </span>The Web Socket protocol</h4>

<p>The <a href=#task-source>task source</a> for all <a href=#concept-task title=concept-task>tasks</a> <a href=#queue-a-task title="queue a
task">queued</a> by algorithms in this section and its
subsections is the <dfn id=web-socket-task-source>Web Socket task source</dfn>.</p>

<h5 id=client-side-requirements><span class=secno>7.3.4.1 </span>Client-side requirements</h5>

<p><em>This section only applies to user agents.</em></p>
<p><em>This section only applies to user agents, not to
servers.</em></p>

<p class=note>This specification doesn't currently define a limit
to the number of simultaneous connections that a client can
Expand Down Expand Up @@ -44225,7 +44226,7 @@ interface <dfn id=websocket>WebSocket</dfn> {
set it to a single character U+002F SOLIDUS (/).</li>

<li><p>If the resulting <a href=#absolute-url>absolute URL</a> has a <a href=#url-query title=url-query>&lt;query&gt;</a> component, then append a
single 003F QUESTION MARK (?) character to <var title="">resource
single U+003F QUESTION MARK (?) character to <var title="">resource
name</var>, followed by the value of the <a href=#url-query title=url-query>&lt;query&gt;</a> component.</li>

<li>
Expand Down Expand Up @@ -44645,7 +44646,7 @@ Proxy-authorization: Basic ZWRuYW1vZGU6bm9jYXBlcyE=</pre>

<li><p>If the high-order bit of <var title="">b</var> is set
(i.e. if <var title="">b</var> <i title="">and</i>ed with 0x80
returns 0x80), then return to the step above labeled <a href=#ws-cd-length>length</a>.</li>
returns 0x80), then return to the step above labeled <a href=#ws-cd-length><i>length</i></a>.</li>

<li><p>Read <var title="">length</var> bytes.</li>

Expand All @@ -44668,7 +44669,7 @@ Proxy-authorization: Basic ZWRuYW1vZGU6bm9jYXBlcyE=</pre>
<li id=ws-cd-data><p><em>Data</em>: Read a byte, let <var title="">b</var> be that byte.</li>

<li><p>If <var title="">b</var> is not 0xff, then append <var title="">b</var> to <var title="">raw data</var> and return to
the previous step (labeled <a href=#ws-cd-data>data</a>).</li>
the previous step (labeled <a href=#ws-cd-data><i>data</i></a>).</li>

<li><p>Interpret <var title="">raw data</var> as a UTF-8
string, and store that string in <var title="">data</var>.</p>
Expand Down Expand Up @@ -44847,15 +44848,15 @@ Proxy-authorization: Basic ZWRuYW1vZGU6bm9jYXBlcyE=</pre>
<li id=ws-sd-data><p><em>Data</em>: Read a byte, let <var title="">b</var> be that byte.</li>

<li><p>If <var title="">b</var> is not 0xff, then append <var title="">b</var> to <var title="">raw data</var> and return to the
previous step (labeled <a href=#ws-sd-data>data</a>).</li>
previous step (labeled <a href=#ws-sd-data><i>data</i></a>).</li>

<li><p>Interpret <var title="">raw data</var> as a UTF-8 string,
and apply whatever server-specific processing should occur for the
resulting string.</p>

<li><p>Return to the first step to read the next byte.</li>

</ol><hr><p>The server should run through the followin steps to send strings
</ol><hr><p>The server should run through the following steps to send strings
to the client:</p>

<ol><li><p>Send a 0x00 byte to the client to indicate the start of a
Expand Down
15 changes: 8 additions & 7 deletions source
Expand Up @@ -50386,7 +50386,7 @@ interface <dfn>WebSocket</dfn> {
</dl>


<h4>The Web Socket protocol</h4>
<h4 id="websocket-protocol">The Web Socket protocol</h4>

<p>The <span>task source</span> for all <span
title="concept-task">tasks</span> <span title="queue a
Expand All @@ -50395,7 +50395,8 @@ interface <dfn>WebSocket</dfn> {

<h5>Client-side requirements</h5>

<p><em>This section only applies to user agents.</em></p>
<p><em>This section only applies to user agents, not to
servers.</em></p>

<p class="note">This specification doesn't currently define a limit
to the number of simultaneous connections that a client can
Expand Down Expand Up @@ -50441,7 +50442,7 @@ interface <dfn>WebSocket</dfn> {

<li><p>If the resulting <span>absolute URL</span> has a <span
title="url-query">&lt;query&gt;</span> component, then append a
single 003F QUESTION MARK (?) character to <var title="">resource
single U+003F QUESTION MARK (?) character to <var title="">resource
name</var>, followed by the value of the <span
title="url-query">&lt;query&gt;</span> component.</p></li>

Expand Down Expand Up @@ -50909,7 +50910,7 @@ Proxy-authorization: Basic ZWRuYW1vZGU6bm9jYXBlcyE=</pre>
<li><p>If the high-order bit of <var title="">b</var> is set
(i.e. if <var title="">b</var> <i title="">and</i>ed with 0x80
returns 0x80), then return to the step above labeled <a
href="#ws-cd-length">length</a>.</p></li>
href="#ws-cd-length"><i>length</i></a>.</p></li>

<li><p>Read <var title="">length</var> bytes.</p></li>

Expand Down Expand Up @@ -50939,7 +50940,7 @@ Proxy-authorization: Basic ZWRuYW1vZGU6bm9jYXBlcyE=</pre>
<li><p>If <var title="">b</var> is not 0xff, then append <var
title="">b</var> to <var title="">raw data</var> and return to
the previous step (labeled <a
href="#ws-cd-data">data</a>).</p></li>
href="#ws-cd-data"><i>data</i></a>).</p></li>

<li><p>Interpret <var title="">raw data</var> as a UTF-8
string, and store that string in <var title="">data</var>.</p>
Expand Down Expand Up @@ -51143,7 +51144,7 @@ Proxy-authorization: Basic ZWRuYW1vZGU6bm9jYXBlcyE=</pre>

<li><p>If <var title="">b</var> is not 0xff, then append <var
title="">b</var> to <var title="">raw data</var> and return to the
previous step (labeled <a href="#ws-sd-data">data</a>).</p></li>
previous step (labeled <a href="#ws-sd-data"><i>data</i></a>).</p></li>

<li><p>Interpret <var title="">raw data</var> as a UTF-8 string,
and apply whatever server-specific processing should occur for the
Expand All @@ -51155,7 +51156,7 @@ Proxy-authorization: Basic ZWRuYW1vZGU6bm9jYXBlcyE=</pre>

<hr>

<p>The server should run through the followin steps to send strings
<p>The server should run through the following steps to send strings
to the client:</p>

<ol>
Expand Down

0 comments on commit 7a01ab4

Please sign in to comment.