RFR [11 8207959 The initial value of SETTINGS_MAX_CONCURRENT_STREAMS should have no limit

[Michael McMahon]

This looks fine, Chris.

- Michael.

On 23/07/2018, 11:43, Chris Hegarty wrote:
> The initial value for the directional parameter SETTINGS_MAX_CONCURRENT_STREAMS,
> in the direction from the server to the client, max concurrent
> client-initiated streams, is incorrectly limited to 100, when there
> should be no initial limit.  Note, the client retains its, configurable,
> limit of 100 server-initiated streams..
>
>  From section 6.5.2. Defined SETTINGS Parameters:
>
>   SETTINGS_MAX_CONCURRENT_STREAMS (0x3): Indicates the maximum number
>        of concurrent streams that the sender will allow. This limit is
>        directional: it applies to the number of streams that the sender
>        permits the receiver to create. *** Initially, there is no limit to
>        this value***. It is recommended that this value be no smaller than
>        100, so as to not unnecessarily limit parallelism.  …
>
>
> https://bugs.openjdk.java.net/browse/JDK-8207959
> http://cr.openjdk.java.net/~chegar/8207959/webrev.00/
>
> A few methods have been renamed in the webrev, to improve
> readability.
>
> -Chris.