W3C home > Mailing lists > Public > ietf-http-wg@w3.org > April to June 2012

Re: Backwards compatibility

From: Adrien W. de Croy <adrien@qbik.com>
Date: Mon, 02 Apr 2012 20:57:56 +0000
To: "Mike Belshe" <mike@belshe.com>, "Mark Watson" <watsonm@netflix.com>
Cc: "<ietf-http-wg@w3.org>" <ietf-http-wg@w3.org>
Message-Id: <em12a686a4-db86-4057-a79b-bfd2eb5f80cb@boist>

------ Original Message ------
From: "Mike Belshe" mike@belshe.com
>On Mon, Apr 2, 2012 at 10:31 AM, Mark Watson <watsonm@netflix.com> wrote:
> All - the messages exchange below was supposed to be on-list - my 
> mistake hitting reply instead of reply-all ...
> On Apr 1, 2012, at 1:15 PM, Mike Belshe wrote:
> >
> > 
 >>Regarding interleaved vs non-interleaved streams:  It sure seems 
 >>easier to do what you're proposing, but I suspect that your proposal 
 >>won't work.  For example, how would you do a comet-style hanging-GET 
 >>without interleaved streams?
>>MW: I'm not familiar with exactly what that is, but I think the 
>>answer is use a separate connection.
>Oh - the browser doesn't know that any given request is a hanging GET, 
>so it can't know to use a separate connection in advance.  You can 
>start forking off new connections for every XMLHttpRequest (since they 
>are more likely to be hanging GETs).  But this is just one of many 
>hacks to make pipelining actually work at all in a real world browser.
>For more info on hanging GETs - check out this:  http://en.wikipedia.org/wiki/Comet_(programming)
>Commonly used for real-time communications like chat.
server push?

Received on Monday, 2 April 2012 20:58:24 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 1 March 2016 11:11:02 UTC