14530 2011-10-21 14:00:16 +0000 Hi, In Server-Sent Events Section "Processing model", it should be clearly stated how to avoid the pipelining of HTTP requests on the connection used for an event source. HTTP pipelining - decribed in RFC 2616 / section 8.1.2.2 - is the possibility for a 2011-10-27 00:03:52 +0000 1 1 1 Unclassified WebAppsWG HISTORICAL - Server-Sent Events (editor: Ian Hickson) unspecified Other other RESOLVED NEEDSINFO http://www.whatwg.org/specs/web-apps/current-work/#top P3 normal --- 1 contributor ian ian mike public-webapps public-webapps-bugzilla oldest_to_newest 58635 0 contributor 2011-10-21 14:00:16 +0000 Specification: http://www.w3.org/TR/eventsource/ Multipage: http://www.whatwg.org/C#top Complete: http://www.whatwg.org/c#top Comment: Hi, In Server-Sent Events Section "Processing model", it should be clearly stated how to avoid the pipelining of HTTP requests on the connection used for an event source. HTTP pipelining - decribed in RFC 2616 / section 8.1.2.2 - is the possibility for a user agent to send a new HTTP request on a connection before the HTTP response of the previous request on the same connection is received. On a connection used for server-sent events, pipelining new HTTP requests cause them to hang forever, since the event stream is potentially infinite. I had this issue recently and some images in my web app were never loaded. I see 2 possible solutions for this type of issue (not necessarily exclusive, of course): 1- it should be clearly stated that a user agent shall not use a connection with a pending text/eventstream typed request for pipelining 2- The server should set a "Connection: close" HTTP header in the event-stream response to prevent any reuse of the same connection by the user agent. This second option solved the issue in my case, but, as I didn't find any guideline on this subject in the current Server-Sent Events draft, I decided to send you this feedback. Hope this can help. Jean-Luc (jean-luc@comimos.com) Posted from: 90.32.162.46 User agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_7_2) AppleWebKit/534.51.22 (KHTML, like Gecko) Version/5.1.1 Safari/534.51.22 58870 1 ian 2011-10-25 05:06:29 +0000 Why would you need to avoid pipelining? 59034 2 ian 2011-10-27 00:03:52 +0000 EDITOR'S RESPONSE: This is an Editor's Response to your comment. If you are satisfied with this response, please change the state of this bug to CLOSED. If you have additional information and would like the editor to reconsider, please reopen this bug. If you would like to escalate the issue to the full HTML Working Group, please add the TrackerRequest keyword to this bug, and suggest title and text for the tracker issue; or you may create a tracker issue yourself, if you are able to do so. For more details, see this document: http://dev.w3.org/html5/decision-policy/decision-policy.html Status: Did Not Understand Request Change Description: no spec change Rationale: see comment 1