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

Re: Extra Connection Support Proposal

From: Kris Zyp <kzyp@sitepen.com>
Date: Tue, 19 Feb 2008 11:58:55 -0700
Message-ID: <0c0d01c87329$7a81f610$4200a8c0@kris>
To: "Maciej Stachowiak" <mjs@apple.com>
Cc: <public-webapi@w3.org>, "Mark Baker" <distobj@acm.org>

> As with pipelining, I think this would be better handled at the HTTP 
> level than the XHR API level. We could define response headers for a 
> server to indicate that it allows more than two connections per  client, 
> or alternately that a specific connection should not count  towards the 
> limit.

I don't have a big problem with this being defined by headers, that seems 
reasonable. It is worth noting that doesn't achieve quite the same effect as 
doing it in XHR since there is time elapsed between the time the request is 
made and the response headers are received. If two connections are currently 
servicing responses, and third connection wishes to declare itself as an 
extra connection, from the client side this could be delivered immediately, 
but with header based permission, it would have to wait it's turn.
That being said, I don't think these are terrible issues, and a fixing it at 
the HTTP level is fine with me.
Received on Tuesday, 19 February 2008 18:59:48 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 21:16:25 UTC