W3C home > Mailing lists > Public > ietf-http-wg@w3.org > January to March 2013

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

From: Martin Thomson <martin.thomson@gmail.com>
Date: Fri, 22 Feb 2013 08:19:47 -0800
Message-ID: <CABkgnnWD1XWx3hChfDh83VmhtspsCHETRnZBYjzM7pCXYa=0Fg@mail.gmail.com>
To: Roberto Peon <grmocg@gmail.com>
Cc: Osama Mazahir <OSAMAM@microsoft.com>, "ietf-http-wg@w3.org Group" <ietf-http-wg@w3.org>
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 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Friday, 22 February 2013 16:20:16 GMT