- From: Kris Zyp <kzyp@sitepen.com>
- Date: Fri, 22 Feb 2008 09:47:35 -0700
- To: "Stewart Brodie" <stewart.brodie@antplc.com>, "Kris Zyp" <kris@sitepen.com>
- Cc: "Anne van Kesteren" <annevk@opera.com>, "Web API WG \(public\)" <public-webapi@w3.org>
> The problem has always existed, though. The problem has always existed, but having long-lived responses for the purpose of the receiving messages from the server massively exacerbates the problem. Most responses are intended to be as short-lived as possible. Also, in the scenario you mentioned, if you click a link on a page with downloads happening, the browser can abort responses for images that are being downloaded, which immediately frees up connections. On the otherhand, if a couple connections are indefinitely open, and you open another tab that needs a connection, the browsers hangs... indefinitely. Kris
Received on Friday, 22 February 2008 16:48:51 UTC