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

Re: http/2 flow control

From: Roberto Peon <grmocg@gmail.com>
Date: Thu, 24 Jan 2013 14:36:40 -0800
Message-ID: <CAP+FsNcFn2HSMRpCZ=c4xvPSpdjJUoAsptcritc6K0KjD4uYuA@mail.gmail.com>
To: Nico Williams <nico@cryptonector.com>
Cc: (wrong string) 陈智昌) <willchan@chromium.org>, HTTP Working Group <ietf-http-wg@w3.org>
Will's naming in his email wasn't the best :)

Flow control in SPDY3 was flawed and didn't work. It was solely per-stream
flow control.
What is proposed in his writeup fixes this flaw relatively simply. The most
relevant line is:

Its important to recognize that stream and session flow control serve two
separate roles. Session flow control helps manage the memory consumption
per session, whereas stream flow control helps manage what portion of that
that memory an individual stream is allowed consume.

I suggest reading the doc, though!

On Thu, Jan 24, 2013 at 2:31 PM, Nico Williams <nico@cryptonector.com>wrote:

> Quick question: is the flow control in SPDY 3 like SSHv2's?  I.e.,
> with per-flow window sizes advertised by the receiver?
> I ask because this has caused serious problems in the SSH world.  I
> don't want HTTP/2.0 to make the same mistakes.
> Nico
> --
Received on Thursday, 24 January 2013 22:37:08 UTC

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