[html5] r2637 - [e] (0) Minor editorial tweaks for WebSocket.
whatwg at whatwg.org
whatwg at whatwg.org
Thu Jan 8 01:58:04 PST 2009
Author: ianh
Date: 2009-01-08 01:58:03 -0800 (Thu, 08 Jan 2009)
New Revision: 2637
Modified:
index
source
Log:
[e] (0) Minor editorial tweaks for WebSocket.
Modified: index
===================================================================
--- index 2009-01-06 12:30:42 UTC (rev 2636)
+++ index 2009-01-08 09:58:03 UTC (rev 2637)
@@ -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-—-date:-01-jan-1901>Draft Recommendation — 6 January 2009</h2>
+ <h2 class="no-num no-toc" id=draft-recommendation-—-date:-01-jan-1901>Draft Recommendation — 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>
@@ -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>
@@ -44180,7 +44180,7 @@
<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
@@ -44188,7 +44188,8 @@
<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
@@ -44225,7 +44226,7 @@
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><query></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><query></a> component.</li>
<li>
@@ -44645,7 +44646,7 @@
<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>
@@ -44668,7 +44669,7 @@
<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>
@@ -44847,7 +44848,7 @@
<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
@@ -44855,7 +44856,7 @@
<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
Modified: source
===================================================================
--- source 2009-01-06 12:30:42 UTC (rev 2636)
+++ source 2009-01-08 09:58:03 UTC (rev 2637)
@@ -50386,7 +50386,7 @@
</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
@@ -50395,7 +50395,8 @@
<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
@@ -50441,7 +50442,7 @@
<li><p>If the resulting <span>absolute URL</span> has a <span
title="url-query"><query></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"><query></span> component.</p></li>
@@ -50909,7 +50910,7 @@
<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>
@@ -50939,7 +50940,7 @@
<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>
@@ -51143,7 +51144,7 @@
<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
@@ -51155,7 +51156,7 @@
<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>
More information about the Commit-Watchers
mailing list