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.

Sign up for GitHub

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

Jump to bottom

WebSocket timeouts to detect connection errors #4

Open
SpComb opened this issue Aug 16, 2016 · 0 comments
Open

WebSocket timeouts to detect connection errors #4

SpComb opened this issue Aug 16, 2016 · 0 comments
Labels
reliability

Comments

@SpComb
Copy link
Member

SpComb commented Aug 16, 2016

Exiting the tally/server will close the WebSocket TCP connection and immediately trigger onClose. Killing the network connection will leave the angularjs client dead with no error indication.

Detecting a loss of network connection needs some kind of websocket ping/pong mechanism.

angular-websocket has a initialTimeout/maxTimeout options, but these only seem to apply to reconnect operations.
@SpComb SpComb changed the title WebSocket timeouts WebSocket timeouts to detect connection errors Aug 16, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
reliability
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@SpComb