[html5] r4378 - [e] (0) Rename the 'reset the connection' operation to 'reestablish the connecti [...]

whatwg at whatwg.org whatwg at whatwg.org
Wed Nov 25 02:15:07 PST 2009 

Author: ianh
Date: 2009-11-25 02:15:05 -0800 (Wed, 25 Nov 2009)
New Revision: 4378

Modified:
   complete.html
   source
Log:
[e] (0) Rename the 'reset the connection' operation to 'reestablish the connection' for clarity.
Fixing http://www.w3.org/Bugs/Public/show_bug.cgi?id=8189

Modified: complete.html
===================================================================
--- complete.html	2009-11-24 04:44:05 UTC (rev 4377)
+++ complete.html	2009-11-25 10:15:05 UTC (rev 4378)
@@ -110,7 +110,7 @@
 
   <header class=head><p><a class=logo href=http://www.whatwg.org/ rel=home><img alt=WHATWG src=/images/logo></a></p>
    <hgroup><h1>Web Applications 1.0</h1>
-    <h2 class="no-num no-toc">Draft Standard — 24 November 2009</h2>
+    <h2 class="no-num no-toc">Draft Standard — 25 November 2009</h2>
    </hgroup><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>
    <!--<p class="impl"><strong>Implementors!</strong> We have a <a href="http://www.whatwg.org/mailing-list#implementors">mailing list</a> for you too!</p>-->
@@ -64633,7 +64633,7 @@
   <p>If such a resource (with the correct <a href=#mime-type>MIME type</a>)
   completes loading (i.e. either the entire HTTP response body is
   received, or the connection is closed somehow, whether by the server
-  or by a network error), the user agent must <a href=#reset-the-connection>reset the
+  or by a network error), the user agent must <a href=#reestablish-the-connection>reestablish the
   connection</a>. This doesn't apply for the error cases that are
   listed below.</p>
 
@@ -64643,11 +64643,11 @@
 
   <p>HTTP 204 No Content, and 205 Reset Content responses are
   equivalent to 200 OK responses with the right <a href=#mime-type>MIME type</a> but no
-  content, and thus must <a href=#reset-the-connection>reset the connection</a>.</p>
+  content, and thus must <a href=#reestablish-the-connection>reestablish the connection</a>.</p>
 
   <p>Other HTTP response codes in the 2xx range <!--201 Created, 202
   Accepted, 203 Non-Authoritative Information, and 206 Partial
-  Content-->must similarly <a href=#reset-the-connection>reset the connection</a>. They
+  Content-->must similarly <a href=#reestablish-the-connection>reestablish the connection</a>. They
   are, however, likely to indicate an error has occurred somewhere and
   may cause the user agent to emit a warning.</p>
 
@@ -64693,7 +64693,7 @@
   task</a> to <a href=#fire-a-simple-event>fire a simple event</a> named <code title=event-open>open</code> at the
   <code><a href=#eventsource>EventSource</a></code> object.</p>
 
-  <p>When a user agent is to <dfn id=reset-the-connection>reset the connection</dfn>, the user
+  <p>When a user agent is to <dfn id=reestablish-the-connection>reestablish the connection</dfn>, the user
   agent must set the <code title=dom-EventSource-readyState><a href=#dom-eventsource-readystate>readyState</a></code> attribute to
   <code title=dom-EventSource-CONNECTING><a href=#dom-eventsource-connecting>CONNECTING</a></code>,
   <a href=#queue-a-task>queue a task</a> to <a href=#fire-a-simple-event>fire a simple event</a> named
@@ -64702,8 +64702,8 @@
   event source resource again after a delay equal to the reconnection
   time of the event source, from the same <a href=#origin>origin</a> as the
   original request triggered by the <code title=dom-EventSource><a href=#dom-eventsource>EventSource()</a></code>
-  constructor. <strong>Only if the user agent <a href=#reset-the-connection title="reset the
-  connection">resets the connection</a> does the connection get
+  constructor. <strong>Only if the user agent <a href=#reestablish-the-connection title="reestablish the
+  connection">reestablishes the connection</a> does the connection get
   opened anew!</strong></p>
 
   <p>When a user agent is to <dfn id=fail-the-connection>fail the connection</dfn>, the user

Modified: source
===================================================================
--- source	2009-11-24 04:44:05 UTC (rev 4377)
+++ source	2009-11-25 10:15:05 UTC (rev 4378)
@@ -73695,7 +73695,7 @@
   <p>If such a resource (with the correct <span>MIME type</span>)
   completes loading (i.e. either the entire HTTP response body is
   received, or the connection is closed somehow, whether by the server
-  or by a network error), the user agent must <span>reset the
+  or by a network error), the user agent must <span>reestablish the
   connection</span>. This doesn't apply for the error cases that are
   listed below.</p>
 
@@ -73705,11 +73705,11 @@
 
   <p>HTTP 204 No Content, and 205 Reset Content responses are
   equivalent to 200 OK responses with the right <span>MIME type</span> but no
-  content, and thus must <span>reset the connection</span>.</p>
+  content, and thus must <span>reestablish the connection</span>.</p>
 
   <p>Other HTTP response codes in the 2xx range <!--201 Created, 202
   Accepted, 203 Non-Authoritative Information, and 206 Partial
-  Content-->must similarly <span>reset the connection</span>. They
+  Content-->must similarly <span>reestablish the connection</span>. They
   are, however, likely to indicate an error has occurred somewhere and
   may cause the user agent to emit a warning.</p>
 
@@ -73760,7 +73760,7 @@
   title="event-open">open</code> at the
   <code>EventSource</code> object.</p>
 
-  <p>When a user agent is to <dfn>reset the connection</dfn>, the user
+  <p>When a user agent is to <dfn>reestablish the connection</dfn>, the user
   agent must set the <code
   title="dom-EventSource-readyState">readyState</code> attribute to
   <code title="dom-EventSource-CONNECTING">CONNECTING</code>,
@@ -73771,8 +73771,8 @@
   time of the event source, from the same <span>origin</span> as the
   original request triggered by the <code
   title="dom-EventSource">EventSource()</code>
-  constructor. <strong>Only if the user agent <span title="reset the
-  connection">resets the connection</span> does the connection get
+  constructor. <strong>Only if the user agent <span title="reestablish the
+  connection">reestablishes the connection</span> does the connection get
   opened anew!</strong></p>
 
   <p>When a user agent is to <dfn>fail the connection</dfn>, the user

More information about the Commit-Watchers mailing list