[html5] r6628 - [e] (0) Mention HTTP codes in the intro. Fixing http://www.w3.org/Bugs/Public/sh [...]
whatwg at whatwg.org
whatwg at whatwg.org
Tue Oct 4 16:34:11 PDT 2011
Author: ianh
Date: 2011-10-04 16:34:09 -0700 (Tue, 04 Oct 2011)
New Revision: 6628
Modified:
complete.html
index
source
Log:
[e] (0) Mention HTTP codes in the intro.
Fixing http://www.w3.org/Bugs/Public/show_bug.cgi?id=13856
Modified: complete.html
===================================================================
--- complete.html 2011-10-04 23:12:04 UTC (rev 6627)
+++ complete.html 2011-10-04 23:34:09 UTC (rev 6628)
@@ -79600,6 +79600,11 @@
data: This is the third message.</pre>
+ <p>Event streams requests can be redirected using HTTP 301 and 307
+ redirects as with normal HTTP requests. Clients will reconnect if
+ the connection is closed; a client can be told to stop reconnecting
+ using the HTTP 204 No Content response code.</p>
+
<p>Using this API rather than emulating it using
<code>XMLHttpRequest</code> or an <code><a href=#the-iframe-element>iframe</a></code> allows the
user agent to make better use of network resources in cases where
Modified: index
===================================================================
--- index 2011-10-04 23:12:04 UTC (rev 6627)
+++ index 2011-10-04 23:34:09 UTC (rev 6628)
@@ -79600,6 +79600,11 @@
data: This is the third message.</pre>
+ <p>Event streams requests can be redirected using HTTP 301 and 307
+ redirects as with normal HTTP requests. Clients will reconnect if
+ the connection is closed; a client can be told to stop reconnecting
+ using the HTTP 204 No Content response code.</p>
+
<p>Using this API rather than emulating it using
<code>XMLHttpRequest</code> or an <code><a href=#the-iframe-element>iframe</a></code> allows the
user agent to make better use of network resources in cases where
Modified: source
===================================================================
--- source 2011-10-04 23:12:04 UTC (rev 6627)
+++ source 2011-10-04 23:34:09 UTC (rev 6628)
@@ -90100,6 +90100,11 @@
data: This is the third message.</pre>
+ <p>Event streams requests can be redirected using HTTP 301 and 307
+ redirects as with normal HTTP requests. Clients will reconnect if
+ the connection is closed; a client can be told to stop reconnecting
+ using the HTTP 204 No Content response code.</p>
+
<p>Using this API rather than emulating it using
<code>XMLHttpRequest</code> or an <code>iframe</code> allows the
user agent to make better use of network resources in cases where
More information about the Commit-Watchers
mailing list