-
-
Notifications
You must be signed in to change notification settings - Fork 429
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
Client Websockets #3545
Client Websockets #3545
Conversation
eaaead6
to
35ad149
Compare
Signed-off-by: Zach Halpern <ZaHalpern+github@gmail.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.
Great addition!
By now the cmake script is considering Qt5::WebSockets an optional (not-mandatory) component, so we should add proper #ifdef QT_WEBSOCKETS_LIB
guards everywhere this Qt framework is used.
Since Qt5::WebSockets is available since Qt 5.3 and we already require 5.5, you can also consider adding it to the required components in the main CMakeLists. This could eventually needs some fixes in the CI build scripts to add the required libraries.
- Remove QWEBSOCEKT_LIB guards - Only TCP on port 4747 - Fix peerName lookup
See Cockatrice/Cockatrice#3545 https://github.com/Cockatrice/Cockatrice/blob/master/cockatrice/src/handle_public_servers.cpp#L74 <br> I also deprecated dr4ft server as it has been down for quite a while and added some cleanup.
Related Ticket(s)
Short roundup of the initial problem
What will change with this Pull Request?