Skip to content
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

Handle when server closes connection after nothing sent for 120s. #1

Open
jconnolly opened this issue Feb 6, 2012 · 0 comments
Open
Assignees

Comments

@jconnolly
Copy link

I'll probably handle this with a keepalive boolean upon initiating the connection, and it will send the keepalive every 60s.

I would still like some sort of coherent message if this happens, regardless. As it stands now, there is no message and if you print messages sent, it will appear that it is indeed attempting to send the messages, but never times out or tells you that the socket connection is not open.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant