W3C home > Mailing lists > Public > ietf-http-wg@w3.org > October to December 2013

Re: https://github.com/http2/http2-spec/issues/329 - Flow control window overflow

From: Roberto Peon <grmocg@gmail.com>
Date: Fri, 6 Dec 2013 12:18:35 -0800
Message-ID: <CAP+FsNdyz1mey-Sd2UNy+QMKDGuTF-U6zeXNG+bKFz9ziaYuWg@mail.gmail.com>
To: Martin Thomson <martin.thomson@gmail.com>
Cc: William Chan (陈智昌) <willchan@chromium.org>, HTTP Working Group <ietf-http-wg@w3.org>, Hasan Khalil <hkhalil@google.com>
Getting flow control detectably wrong should cause the connection to be
torn down. RST_STREAM doesn't cut it.
-=R


On Fri, Dec 6, 2013 at 11:54 AM, Martin Thomson <martin.thomson@gmail.com>wrote:

> On 6 December 2013 11:42, William Chan (陈智昌) <willchan@chromium.org>
> wrote:
> > Hasan is in favor of GOAWAY, and FWIW I agree.
>
> I think that a stream error would potentially cause problems with
> connection-level flow control if you aren't careful.  It seems better
> to err on the side of caution.
>
> > Presumably Hasan will use the FLOW_CONTROL_ERROR status code here, but I
> dunno.
>
> That sounds fine, though I don't like to second-guess Hasan.  Maybe
> the code he chooses will be covered in awesome.
>
>
Received on Friday, 6 December 2013 20:19:02 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 1 March 2016 11:11:20 UTC