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

Re: HEADERS and flow control

From: Mark Nottingham <mnot@mnot.net>
Date: Mon, 19 May 2014 17:41:48 +1000
Cc: HTTP Working Group <ietf-http-wg@w3.org>
Message-Id: <0E01520E-F925-4BF8-8898-BD331955ECF7@mnot.net>
To: Roberto Peon <grmocg@gmail.com>

Ive opened <https://github.com/http2/http2-spec/issues/480> to track this.

Well discuss this in NYC (although please do continue discussing on-list). 

Be warned that a large amount of the discussion around this will be Is this worth holding HTTP/2 for another implementation draft / implementation / interop cycle?


On 10 May 2014, at 4:42 am, Roberto Peon <grmocg@gmail.com> wrote:

> 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 asserted.
> 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.
> Thoughts?
> -=R

Mark Nottingham   http://www.mnot.net/
Received on Monday, 19 May 2014 07:42:17 UTC

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