W3C home > Mailing lists > Public > public-webapps@w3.org > July to September 2012

Re: [Server-Sent Events] Network connection clarification

From: Neil Jenkins <neilj@opera.com>
Date: Thu, 19 Jul 2012 08:52:31 +0100
Message-Id: <1342684351.28140.140661103944745.4B7F7F7F@webmail.messagingengine.com>
To: public-webapps@w3.org
Cc: Odin Hørthe Omdal <odinho@opera.com>
On Tue, 17 Jul 2012, at 09:06 AM, Arthur Barstow wrote:
> Neil, Hixie, Chaals, All, - I don't see a clear conclusion/consensus and 
> no bug was filed. As such, please indicate - via a reply to the 
> _original_ thread - your take on this comment and please file a bug if 
> applicable.

I think all replies to this comment concurred that UAs are better placed
to handle reconnection after network loss, as they have access to
OS-level network connectivity information so can trigger a reconnect as
soon as the device regains network access. I also believe that most web
developers will find the currently specified behaviour unintuitive
(indeed, looking at Odin's analysis of existing UA behaviour, it's clear
that UA implementors also either misunderstood or deliberately ignored
this part of the spec). I can't see any use case where you *wouldn't*
want to reconnect again after network loss, so by prohibiting this in
the spec, you're forcing developers to continually re-implement the same
behaviour, but with less information available to them than the UA has.
And of course, most developers won't even realise and/or bother to do
so, leading to breakage of apps whenever there's a network hiccup.

This is a serious flaw in the spec and should be fixed for version one;
it is however the same issue as Odin raised, so we only need a single
bug to cover the two comments. Odin has already created
https://www.w3.org/Bugs/Public/show_bug.cgi?id=18320; I will simply
add my comments there.

Neil.
Received on Thursday, 19 July 2012 07:53:06 GMT

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