- From: CVS User ihickson <cvsmail@w3.org>
- Date: Wed, 02 Jan 2013 22:23:39 +0000
- To: public-html-commits@w3.org
Update of /sources/public/html5/eventsource
In directory roscoe:/tmp/cvs-serv24195
Modified Files:
Overview.html
Log Message:
Since this made it likely that overloaded servers would just get even more overloaded, pull back a little and let all 5xx errors stop EventSource reconnects. It still reconnects if the connection drops, though. (Compat: 5xxs don't cause reconnects in deployed browsers currently as far as I can tell.) (whatwg r7634)
--- /sources/public/html5/eventsource/Overview.html 2012/12/04 23:56:06 1.233
+++ /sources/public/html5/eventsource/Overview.html 2013/01/02 22:23:39 1.234
@@ -216,7 +216,7 @@
<h1>Server-Sent Events</h1>
- <h2 class="no-num no-toc" id="editor-s-draft-4-december-2012">Editor's Draft 4 December 2012</h2>
+ <h2 class="no-num no-toc" id="editor-s-draft-2-january-2013">Editor's Draft 2 January 2013</h2>
<dl><dt>Latest Published Version:</dt>
<dd><a href="http://www.w3.org/TR/eventsource/">http://www.w3.org/TR/eventsource/</a></dd>
<dt>Latest Editor's Draft:</dt>
@@ -354,7 +354,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 4 December 2012 Editor's Draft.
+ This specification is the 2 January 2013 Editor's Draft.
</p>
@@ -741,13 +741,12 @@
resource for this <code><a href="#eventsource">EventSource</a></code> object start with the URL given for the last 301 seen
for requests for this object.</p>
- <p>HTTP 500 Internal Server Error, 502 Bad Gateway, 503 Service Unavailable, and 504 Gateway
- Timeout responses, and any network error that prevents the connection from being established in
- the first place (e.g. DNS errors), must cause the user agent to asynchronously <a href="#reestablish-the-connection">reestablish
- the connection</a>.</p>
+ <p id="event-source-network-errors-reconnect">Network errors that prevents the connection from
+ being established in the first place (e.g. DNS errors), must cause the user agent to
+ asynchronously <a href="#reestablish-the-connection">reestablish the connection</a>.</p>
- <p>Any other HTTP response code not listed here must cause the user agent to <a href="#fail-the-connection">fail the
- connection</a>.</p>
+ <p id="event-source-fail-reasons">Any other HTTP response code not listed here must cause the user
+ agent to <a href="#fail-the-connection">fail the connection</a>.</p>
<p>For non-HTTP protocols, UAs should act in equivalent ways.</p>
Received on Wednesday, 2 January 2013 22:23:40 UTC