Re: [hybi] permessage-deflate parameter negotiation

Yes. For options where

1. The receiver could still correctly decode the frames if it ignored the
option, but
2. The receiver could take advantage of the option to save resources

I think it makes sense to encourage the sender to specify those options,
even if unsolicited. The sender will be compliant even if it locally
applies those options without telling the receiver about it, but the
receiver can benefit from knowing about it.

On 14 June 2013 19:25, Takeshi Yoshino <tyoshino@google.com> wrote:

> As we're going to allow unsolicited s2c_no_context_takeover and
> s2c_max_window_size, maybe we should also allow client to send
> c2s_no_context_takeover and c2s_max_window_size if it wants.
>
> Existing client->server c2s_max_window_size without value can be kept.
> I.e.:
> - Empty client->server c2s_max_window_size means that the client can
> accept c2s_max_window_size.
> - client->server c2s_max_window_size with value X means that the client
> can accept c2s_max_window_size and even if the server won't send any
> server->client c2s_max_window_size, the client won't use window size larger
> than X.
>
>
> _______________________________________________
> hybi mailing list
> hybi@ietf.org
> https://www.ietf.org/mailman/listinfo/hybi
>
>