- From: Roberto Peon <grmocg@gmail.com>
- Date: Fri, 9 May 2014 12:10:45 -0700
- To: Martin Thomson <martin.thomson@gmail.com>
- Cc: HTTP Working Group <ietf-http-wg@w3.org>
Received on Friday, 9 May 2014 19:11:16 UTC
What creates a surprising corner case? Lets put it another way. HEADERS which establish streams are control frames. HEADERS which are in the middle of a stream, however, despite being control frames are NOT doing any controlling. They are payload. -=R On Fri, May 9, 2014 at 12:02 PM, Martin Thomson <martin.thomson@gmail.com>wrote: > On 9 May 2014 11:42, Roberto Peon <grmocg@gmail.com> wrote: > > 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. > > /me needs more information. > > This is unlikely to affect most use cases, but it does create another > potentially surprising corner case. I think that I need (much) > stronger justification. >
Received on Friday, 9 May 2014 19:11:16 UTC