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
[ADDED] Support for Websocket protocol #719
Conversation
This is in preparation before adding WS support. Signed-off-by: Ivan Kozlovic <ivan@synadia.com>
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 - Like the way you have organized things, will serve us well IMO.
Any data on performance changes?
Very exciting :) |
LGTM, also curious about performance |
Not sure if you are asking about performance of WS or impact of refactoring on non WS. For the later, quick dirty test. From master:
From
So really no impact on this test.
|
Amazing. |
That's awesome. |
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. Nice!
Hi guys, thanks for your work. Just some questions
|
Signed-off-by: Ivan Kozlovic <ivan@synadia.com>
@mirusky Thanks! We actually going to likely merge this in the main branch once the review is complete and Websocket will be part of the upcoming v1.11.0 release. |
@ColinSullivan1 Please have a look at c8c0b60 and see if it helps. |
LGTM - thanks Ivan! |
Websocket protocol will be used as long as the URL scheme is
ws
orwss
.Note that no mixing of websocket and non-websocket URLs can be used (in the list of servers). Once a client connects, the gossip will be augmenting the URLs of that "type".
A
Compression()
option was added, which is currently documented as being used only for Websocket connections.