Re: [hybi] permessage-deflate and missing asymmetric configurations

The spec allows disabling compression on a per message basis. To do what you describe a server could simply negotiate compression per the client's request then not send any compressed frames or create any compression contexts for itself.

There may be some additional resource savings possible if an endpoint knows it will never receive a compressed message. That should be considered at least.

On Oct 9, 2013, at 13:48 , Joakim Erdfelt <joakim@intalio.com> wrote:

> One important aspect missing from the asymmetric configurations for permessage-deflate is the lack of disabling the compression.
> 
> It would be ideal to allow an asymmetric connection where, for example the client is talking compressed, but the server is not. (or vice versa)
> 
> Why is this feature not present in the spec?
> 
> 
> --
> Joakim Erdfelt <joakim@intalio.com>
> webtide.com - intalio.com/jetty
> Expert advice, services and support from from the Jetty & CometD experts
> eclipse.org/jetty - cometd.org
> _______________________________________________
> hybi mailing list
> hybi@ietf.org
> https://www.ietf.org/mailman/listinfo/hybi