- From: Mark Nottingham <mnot@mnot.net>
- Date: Mon, 19 May 2014 17:41:48 +1000
- To: Roberto Peon <grmocg@gmail.com>
- Cc: HTTP Working Group <ietf-http-wg@w3.org>
Roberto, I’ve opened <https://github.com/http2/http2-spec/issues/480> to track this. We’ll 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?” Cheers, 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