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

Re: HEADERS and flow control

From: Ilari Liusvaara <ilari.liusvaara@elisanet.fi>
Date: Wed, 21 May 2014 18:53:54 +0300
To: Michael Sweet <msweet@apple.com>
Cc: 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>
Message-ID: <20140521155354.GA2230@LK-Perkele-VII>
On Wed, May 21, 2014 at 10:32:25AM -0400, Michael Sweet wrote:
> +1
> 
> Even with the current header compression, there is no reason to prevent
> intervening DATA frames, or to omit HEADER frames from the
> scheduling/queuing algorithms that clients and servers must implement
> for HTTP/2.  The only requirement based on the header compression
> algorithm that has been adopted is that there can only be a single set
> of HEADER frames in flight in either direction, and I don't think that
> is a big step beyond what is already required.

Well, this is probably fundamentially ill-defined question, but:

What are the semantics of DATA frames transmitted on stream with HEADER
block still active? If the HEADER is the first header block? If the HEADER
is subsequent HEADER block?


-Ilari
Received on Wednesday, 21 May 2014 15:54:20 UTC

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