Re: #40 - HTTP2 default value for client supported max_concurrent_streams

On 22 February 2013 05:29, Roberto Peon <grmocg@gmail.com> wrote:
> What is the motivation for that?

I'm not suggesting that this is Osama's motivation, but look at the
Upgrade scenario: the server is the first to send on the HTTP/2.0
session with a response.  There's an obvious opportunity there to push
prior to the client SETTINGS frame arriving.  The TLS scenario is less
interesting - the client sends SETTINGS prior to any request, making
defaults non-interesting.

Received on Friday, 22 February 2013 16:20:14 UTC