Re: #38 - HTTP2 min value for server supported max_concurrent_streams

[Martin Thomson <[e-mail]>]

On 22 February 2013 05:18, Roberto Peon <[e-mail]> wrote:
> Why 1?

1 seems a little restrictive, especially since 6 concurrent
connections is the current expectation in many browsers.

> If a client sends 8 concurrent streams, and the server only wants to handle
> 6 (say, because it is particularly resource limited right now), then it will
> reset two of the streams with an error code that essentially says
> try-again-later, and it can do so after sending the SETTINGS frame.

This is not isomorphic with a lower stream limit simply because the
client will have sent some amount of data for the 2 rejected streams,
expending some of what is a fairly limited resource (INIT CWD being as
it is).  That's probably OK if you consider that it's the client
prerogative and responsibility.