-
-
Notifications
You must be signed in to change notification settings - Fork 718
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
WebSocket permessage-deflate extension support #770
Labels
feature
New feature or request
Comments
Hi! yeah, see snapview/tungstenite-rs#144 |
See snapview/tungstenite-rs#235. To support |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Sec-WebSocket-Extensions: permessage-deflate
and such is available in Firefox and Chrome, and utilizing it natively would eliminate the need to load large JavaScript decompression libraries on the client-side. (Large as in about 28KB min-gzipped)The native implementation in-browser is probably faster than Javascript codecs as well.
Ideally, this could be automatic, as the compression is transparent. However, it should also be able to signal to the user code that compression extensions are unavailable, so it could fallback and signal to load those aforementioned libraries.
The alternative would be to just continue doing it manually. I'm simply using
flate2
and sending/receiving binary messages.Perhaps this is more an issue for tokio-tungstenite?
The text was updated successfully, but these errors were encountered: