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

Re: HEADERS and flow control

From: Martin Thomson <martin.thomson@gmail.com>
Date: Wed, 21 May 2014 10:48:47 -0700
Message-ID: <CABkgnnVtDWzFpanPBkVzsgMypdJv3QhH=KQx9m7xXqr6vWvTgw@mail.gmail.com>
To: Michael Sweet <msweet@apple.com>
Cc: Ilari Liusvaara <ilari.liusvaara@elisanet.fi>, Greg Wilkins <gregw@intalio.com>, David Krauss <potswa@gmail.com>, Mark Nottingham <mnot@mnot.net>, Roberto Peon <grmocg@gmail.com>, HTTP Working Group <ietf-http-wg@w3.org>
On 21 May 2014 10:21, Michael Sweet <msweet@apple.com> wrote:
> On a given stream you won't see DATA frames until all of the HEADER frames have been sent (or received).
> But if you are in the middle of sending HEADER frames to create a new stream (or for response headers), DATA frames for existing streams can continue to flow - semantically they are separate streams with separate state.

That is one possible design.  So far, each time this has been
proposed, it has not garnered any real support.  Big header blocks
will cause head of line blocking, but the answer we have thus far
chosen, is to say "don't do that then".
Received on Wednesday, 21 May 2014 17:49:15 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 17:14:30 UTC