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).
The text was updated successfully, but these errors were encountered: