New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Investigate a data compressing extension #558

Open
sbordet opened this Issue Oct 8, 2014 · 2 comments

Comments

Projects
None yet
2 participants
@sbordet
Member

sbordet commented Oct 8, 2014

HTTP transports can compress the whole body (which can be made of multiple Bayeux messages) selectively for bodies bigger than a threshold (e.g. Jetty's GzipFilter).
This is a great feature and has been proven to be really outstanding in real-world deployments.

WebSocket transports can't typically compress multiple messages (as typically each Bayeux message is sent in one WebSocket frame); The permessage-deflate extension can compress single messages, but cannot do so selectively. Compression in WebSocket is either totally on or totally off.

Perhaps there is value in providing a CometD extension for large application data, where the application data is compressed (selectively only if bigger than a threshold).

@sbordet

This comment has been minimized.

Show comment
Hide comment
@sbordet

sbordet Oct 8, 2014

Member

Originally reported by sbordet on 2014-10-08T06:44:02Z

Member

sbordet commented Oct 8, 2014

Originally reported by sbordet on 2014-10-08T06:44:02Z

@jakefreeberg

This comment has been minimized.

Show comment
Hide comment
@jakefreeberg

jakefreeberg commented Sep 9, 2016

👍

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment