Re: [#150] Making certain settings mandatory

[Mike Belshe <[e-mail]>]

I believe the bytes are completely inconsequential.

My goal with this was to make it so there is only one set of rules for
SETTINGS frames.  Currently, there is the "oh this is the first settings
frame rules".

This is not going to have impact on performance, but removing edge cases is
desirable to me.

Mike



On Thu, Jun 27, 2013 at 10:27 AM, Martin Thomson
<[e-mail]>wrote:

> This pull request proposes to make two settings mandatory in every
> SETTINGS frame: SETTINGS_MAX_CONCURRENT_STREAMS and
> SETTINGS_INITIAL_WINDOW_SIZE.
>
> https://github.com/http2/http2-spec/pull/150
>
> Gabriel's proposal for an HTTP/1.1 header for carrying settings in the
> Upgrade made these mandatory only at that point, which didn't cover
> the TLS handshake, or just starting from prior knowledge.
>
> Two questions:
>  - Do we want to make any settings mandatory, or are defaults acceptable?
>  - Is this the right trade-off? Or are the 16 bytes on subsequent
> SETTINGS frames completely intolerable.
>
> Note that if we make these settings mandatory, there might be other
> settings in the future that will also be mandatory; e.g., the
> compression context size.
>
>