Re: Security Condideration of initial SETTINGS_MAX_CONCURRENT_STREAMS

On 14 January 2014 17:55, Shigeki Ohtsu <ohtsu@iij.ad.jp> wrote:
> One idea is to define an initial SETTINGS_MAX_CONCURRENT_STREAMS such as 100
> which is recommended as minimum in the current spec.
> Is there any reason not to define it?

I've always wondered the same thing.

Is there anyone out there who thinks it possible to even get 100
requests into the second round trip TCP congestion window for any
reasonable use case?

Received on Wednesday, 15 January 2014 17:47:51 UTC