Opt-in on message compression

[hustf]

Compression extensions are standardized by now.
For local websockets, the current behaviour of not compressing messages is optimal.
For use over the internet, compression is a necessary feature for e.g. interactive pixel graphics.

On the client side, the negotiated message compression is available in javascript using
websocket.extensions. A similar interface ought to be available on the server side.

The http request for a websocket contains the possibilities, e.g. from Chrome:
Sec-WebSocket-Extensions => permessage-deflate; client_max_window_bits

Ref. issue #76 - compression would currently be very effective even on local connections.

[crazbot]

is "permessage-deflate“ implemented?

[hustf]

No it is not. It would be a straightforward addition to make, but just currently we are sitting on the fence a bit to see if httpserver will have a 0.7 version or not. I think there is something of the same issue over at HTTP.jl. Try to search for issues there. Den lør. 30. jun. 2018, 12:07 skrev harrse <[email protected]>:

…

is "permessage-deflate“ implemented? — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#78 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ANTatBsEdsXHvFHKvf4PZGhcA2fSXLXFks5uB039gaJpZM4QcTCC> .