Skip to content

Document reconnect_after option in net.box:new #33

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

Closed
mejedi opened this issue Aug 18, 2016 · 0 comments
Closed

Document reconnect_after option in net.box:new #33

mejedi opened this issue Aug 18, 2016 · 0 comments
Assignees

Comments

@mejedi
Copy link
Contributor

mejedi commented Aug 18, 2016

With reconnect_after <timeout> option, net.box instance will automatically reconnect any time the connection is broken or if a connection attempt fails. The number of retries is unlimited. Once a connection is explicitly closed (or garbage-collected), reconnects stop.

Assume application maintains a connection to server X. With reconnect_after, transient network failures become transparent to the application. Reconnect happens automatically in the background and queries/requests that suffered due to connectivity loss are transparently retried.

In the presense of reconnect_after, wait_connected ignores transient failures. The wait completes once the connection is established or is closed explicitly.

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

2 participants