W3C home > Mailing lists > Public > public-webapi@w3.org > February 2008

Re: Extra Connection Support Proposal

From: Kris Zyp <kris@sitepen.com>
Date: Wed, 27 Feb 2008 12:54:34 -0700
Message-ID: <0bdf01c8797a$94dbc160$4200a8c0@kris>
To: "Jonas Sicking" <jonas@sicking.cc>, "Stewart Brodie" <stewart.brodie@antplc.com>
Cc: "Anne van Kesteren" <annevk@opera.com>, "Kris Zyp" <kzyp@sitepen.com>, "Web API WG \(public\)" <public-webapi@w3.org>

>> you click on a link, does the link get followed?  That is the same sort 
>> of
>> scenario, isn't it?
>
> At least firefox will abort any existing downloads for the current page 
> when the user clicks a link. But if you're downloading these images in 
> another tab you might have this problem yeah. Though if it's simply 
> multiple images the new page will likely get squeezed in between two of 
> the image downloads.
And there is an important distinction between images being downloaded that 
consume connections and a long-lived response that consume a connection. 
With normal responses, two connection usually provides a means for 
relatively continuous utilization of resources. Most of the time two 
connections provide enough requests that the usually the server is 
processing a request, or a response is downloading. Either way, something is 
being done, and it is quite reasonable for further requests to be queued, 
since the server/connection is working to finish the response as fast as 
possible within it's capability. On the otherhand, when a long-lived 
response is paused indefinitely until a the server has a message to be sent, 
there is nothing being done. Nothing is being downloaded, and the server 
isn't working on anything, and requests can be queued indefinitely even 
though nothing is happening.
Kris 
Received on Wednesday, 27 February 2008 19:56:21 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Wednesday, 27 February 2008 19:56:23 GMT