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

Consider adding property like supportsKeepAliveReconnectTimeout on client, when it is true then on client KeepAlive can stop to reconnect once reconnect timestamp great than the timeout, and stop the connection. #825

Closed
Xiaohongt opened this issue Oct 19, 2012 · 1 comment

Comments

@Xiaohongt
Copy link
Contributor

Currently when the network become disconnected, the client KeepAlive will try to reconnect again again forever, but on server side when the connection timeout, server close the connection, but the client still try to reconnect until the network get connected then client disconnect the connection.

If we add property like supportsKeepAliveReconnectTimeout on client, by default we can set it to false, so client still have the same old behavior.
When supportsKeepAliveReconnectTimeout set to true, then client KeepAlive can stop to reconnect once reconnect timestamp great than the timeout, and the timeout by default we can set the value same as the server connection timeout or bigger.

@DamianEdwards
Copy link
Member

This can be achieved by app devs already by handling the reconnect event and calling connection.stop() themselves.

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

No branches or pull requests

2 participants