-
Notifications
You must be signed in to change notification settings - Fork 722
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
How to emit with TLS mode #19
Comments
I don't need this line in my project: h.socket()->on("pong", (sio::socket::event_listener)&OnMessage); Have you seen the console example? I was able to modify that for my needs. Currently running C++ and Javascript clients with a Node.js server in between. |
|
I found the error in my code from your console example. I'll close the issue and thanks for the response! |
I am working with the modified console example. The emit works and is received on the server side, I am also noticing a message every time I emit, I get the console message;
The message comes from within client_impl::ping would this be related to ping interval or ping timeout setting? |
Thanks for including TLS.
I was having trouble emitting a simple message using the following code, I am probably doing something wrong;
The server side does not obtain the emitted message "ping".
The console reports:
The part about "close by reason" is a cause of concern, I tried looking through the code but I'm not sure what would cause this.
The text was updated successfully, but these errors were encountered: