W3C home > Mailing lists > Public > public-webapps@w3.org > January to March 2013

Server-Sent Events contradiction

From: Bill Thiede <w3@xinu.tv>
Date: Sun, 30 Dec 2012 19:20:54 -0800
To: public-webapps@w3.org
Message-ID: <20121231032054.GA25358@xinu.tv>
The Server-Sent Events at http://www.w3.org/TR/2012/CR-eventsource-20121211/
states under the IANA considerations / Security considerations section:

"Servers can be overwhelmed if a situation develops in which the server is
causing clients to reconnect rapidly. Servers should use a 5xx status code to
indicate capacity problems, as this will prevent conforming clients from
reconnecting automatically."

However, under section "5 Processing model" it is stated:

"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 reestablish the connection."

My guess is section 5 was updated more recently and the IANA section was
overlooked.  I know there are 5xx errors not listed explicitly, which would
then trigger the "Any other HTTP response code not listed here must cause the
user agent to fail the connection," but I doubt that a 501 or 505 are the
suggested solution here.

Bill

PS I'm emailing, because the 'Feedback Comments' form on the web page returned
'ERROR' on my attempt to submit.  Not sure who to notify of that problem.
Received on Wednesday, 2 January 2013 18:34:24 GMT

This archive was generated by hypermail 2.3.1 : Tuesday, 26 March 2013 18:49:57 GMT