- From: <bugzilla@jessica.w3.org>
- Date: Tue, 10 Jan 2012 16:17:45 +0000
- To: public-webapps@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=15495 Summary: I need some way of recovering from longer but still temporary failures, without requiring a complete page refresh, and without requiring every all events of interest to be rebound, or otherwise handled differently from any other event. This isn't an issue Product: WebAppsWG Version: unspecified Platform: Other URL: http://www.whatwg.org/specs/web-apps/current-work/#top OS/Version: other Status: NEW Severity: normal Priority: P3 Component: Server-Sent Events (editor: Ian Hickson) AssignedTo: ian@hixie.ch ReportedBy: contributor@whatwg.org QAContact: member-webapi-cvs@w3.org CC: mike@w3.org, public-webapps@w3.org Specification: http://www.w3.org/TR/eventsource/ Multipage: http://www.whatwg.org/C#top Complete: http://www.whatwg.org/c#top Comment: I need some way of recovering from longer but still temporary failures, without requiring a complete page refresh, and without requiring every all events of interest to be rebound, or otherwise handled differently from any other event. This isn't an issue with the WebSocket and XMLHttpRequest API's, as those interfaces already require one to implement an event passing scheme on top, making it trivial to replace the underlying WebSocket or XMLHttpRequest. While such a scheme could also be implemented on top of EventSource, it seems silly to stack an different event source scheme on top of something called "EventSource". Posted from: 70.64.129.37 User agent: Mozilla/5.0 (X11; Linux i686) AppleWebKit/535.2 (KHTML, like Gecko) Ubuntu/10.04 Chromium/15.0.874.106 Chrome/15.0.874.106 Safari/535.2 -- Configure bugmail: https://www.w3.org/Bugs/Public/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
Received on Tuesday, 10 January 2012 16:17:48 UTC