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

Re: HEADERS and flow control

From: Michael Sweet <msweet@apple.com>
Date: Wed, 21 May 2014 13:24:14 -0400
Cc: Greg Wilkins <gregw@intalio.com>, Mark Nottingham <mnot@mnot.net>, Roberto Peon <grmocg@gmail.com>, HTTP Working Group <ietf-http-wg@w3.org>
Message-id: <A1563DEC-68A4-496C-9EE8-77BE00DA1535@apple.com>
To: David Krauss <potswa@gmail.com>

On May 21, 2014, at 12:01 PM, David Krauss <potswa@gmail.com> wrote:
> ...
> Decoding takes resources even with a stateless compressor, because the in-flight header set needs to exist in memory. With the current algorithm, the server can at least hope that having a complete header set, and beginning to service the request, will free up resources to handle a new header set.

I'm not suggesting that implementations need to track multiple header sets, just the 2 as required today (one "up" and one "down").  All I am saying is that preventing intervening DATA frames is unnecessary for the compressor that has been chosen, and that already-established streams should not be held up for a set of HEADER frames.

Michael Sweet, Senior Printing System Engineer, PWG Chair

Received on Wednesday, 21 May 2014 17:24:45 UTC

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