-
Notifications
You must be signed in to change notification settings - Fork 254
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 connection does not seem to be persistent #2
Comments
It is supposed to remain open, and does in my usage (which hasn't been so extensive yet). Can you reproduce this towards a public websocket, for example echo.websocket.org? |
It seems that I can not reproduce this issue anymore as well. Maybe it was just a mistake on my side. |
Ok; I was thinking otherwise that it could be a server sending a PING to confirm the connection, closing it since I have not yet implemented PING :) |
Reopen if you can reproduce. |
I observe the following behaviour in my application -
1.) the client connects to a server through a websocket
2.) the client receives a message from the server, and answers
3.) the server loses connection to the client
optimally, I would like to keep the connection open, because my communication is not stateless, can I do that? =)
Thanks
The text was updated successfully, but these errors were encountered: