-
Notifications
You must be signed in to change notification settings - Fork 664
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
[UPDATED] Compression library for Websocket #1259
Conversation
Signed-off-by: Derek Collison <derek@nats.io>
Signed-off-by: Derek Collison <derek@nats.io>
Signed-off-by: Derek Collison <derek@nats.io>
With compress/flate, it seems that after calling Close() it was fine dropping the last 4 bytes before doing the framing, but with the different flate, it fails. Instead, use Flush() (like in the server) and then dropping the last 4 bytes works as before. I have added a compression.Close() on connection close, after sending the CLOSE frame. Signed-off-by: Ivan Kozlovic <ivan@synadia.com>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM!
A couple of failing tests, might be flappers or might be due to upgrade of underlying server. I doubt related to WS compression. |
Can someone take a look at |
I'll take a look at it |
I found some issues in object store and fixed them here: #1260. They had nothing to do with this PR, so I'll merge it now. |
Signed-off-by: Derek Collison derek@nats.io
Signed-off-by: Ivan Kozlovic ivan@synadia.com