- From: <bugzilla@jessica.w3.org>
- Date: Wed, 18 Jul 2012 22:30:48 +0000
- To: public-webapps-bugzilla@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=18320 Summary: Clarify how reconnection works when loosing internet connection Product: WebAppsWG Version: unspecified Platform: All OS/Version: All Status: NEW Severity: normal Priority: P2 Component: Server-Sent Events (editor: Ian Hickson) AssignedTo: ian@hixie.ch ReportedBy: odinho@opera.com QAContact: public-webapps-bugzilla@w3.org CC: mike@w3.org, public-webapps@w3.org Currently browsers (Opera, Firefox, Chromium) reconnect when they loose their connection. Opera only tries a few times and a very short time, whilst Firefox retries for around 15 minutes before giving up. Chromium keeps it going indefinitely. They do an exponential increase of the wait time. Up to a max. A smarter implementation would also listen to "network up" events from the OS etc. Second discussion: [2] http://lists.w3.org/Archives/Public/public-webapps/2012AprJun/0399.html (Something wrong with archive, so here is the rest of the thread:) [3] http://lists.w3.org/Archives/Public/public-webapps/2012JulSep/thread.html#msg82 First discussion: [1] http://lists.w3.org/Archives/Public/public-webapps/2012AprJun/0226.html As discussed in the email threads ([3],and in [1]), it would also make sense to notify of this state. In that way authors will be able to handle the reconnect on their own if they want: es.onreconnecting = function(e) { // es.readyState is EventSource.RECONNECTING // We don't want the default behaviour es.close(); do_custom_reconnecting_logic(); }; -- Configure bugmail: https://www.w3.org/Bugs/Public/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the QA contact for the bug.
Received on Wednesday, 18 July 2012 22:30:51 UTC