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

HEADERS and flow control

From: Roberto Peon <grmocg@gmail.com>
Date: Fri, 9 May 2014 11:42:18 -0700
Message-ID: <CAP+FsNfWVtRnStkfd9jbKJitiv-dYf3LRAoSBMoGP04FsgxkLw@mail.gmail.com>
To: HTTP Working Group <ietf-http-wg@w3.org>
Currently HEADERS are not subject to flow control. There are a couple of
reasons for this, but the biggest one is that this helps to prevent a
deadlock which can occur when a server is waiting for a particular request
before it can make progress on other responses, but flow control is

One of the potential users of HTTP2 whom I've spoken with wished strongly
that HEADERS after the first complete HEADERS block on a stream would be
subject to flow control. AFAICT, this would work better than what we have
today, without potentially triggering the deadlock scenario for many
non-browser usecases.


Received on Friday, 9 May 2014 18:42:44 UTC

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