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

How to check if client is still connected? #316

Closed
shirofuji opened this issue May 19, 2015 · 1 comment
Closed

How to check if client is still connected? #316

shirofuji opened this issue May 19, 2015 · 1 comment
Labels

Comments

@shirofuji
Copy link

How do i check if the client is still connected to the Ratchet server? I tried opening multiple instance of my client using browser tabs and closed them using taskkill, unfortunately the onclose function of my server did not trigger. My server is fully based on the push integration sample on http://socketo.me

@cboden
Copy link
Member

cboden commented May 19, 2015

See #70 on why this happens. You can resolve this in one of two ways: use a reverse proxy for your WebSocket server (nginx) and have a TCP timeout on it. Another option would be to implement your own heartbeat, see #263 for an example of someone doing this.

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

No branches or pull requests

2 participants