Provide a way to limit HTTP/2 initial max concurrent streams by a client

A client can make more streams than the server allows and send them before it gets the HTTP/2 settings frame from the server. We need a way to limit the number:

ClientFactory.builder()
             .http2InitialMaxConcurrentStreams()
             /* .http2MaxConcurrentStreams() Will be added when server push is implemented */
             ...

[minwoox]

What would a user specify in Http2Settings besides the max number of concurrent streams?

Not so much? 🤣 I thought there’s a chance that a user wants to set the properties such as maxFrameSize, initialWindowSize and etc before the client gets the settings frame, but probably that’s overkill. So specifying http2InitialMaxConcurrentStreams would be enough I guess.

[minwoox]

Speaking of max concurrent streams, I think the method name for setting the max current streams server-side can be mistakenly considered. (Server.builder().http2MaxStreamsPerConnection) I hope we can change it to http2MaxConcurrentStreams when we reach 2.0.