We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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鈥檒l occasionally send you account related emails.
Already on GitHub? Sign in to your account
Currently, when using automaticReconnectWithDefaultConfig, the client may hang indefinitely if it can't reconnect to the broker.
automaticReconnectWithDefaultConfig
As pointed out (and requested by @dowhiletrue in #302), users would like the ability to configure this behavior to either:
There are three options on top of my mind: block throw continue and try to connect later Which option fits best depends on the use-case. Make the behavior configurable?
There are three options on top of my mind:
Which option fits best depends on the use-case. Make the behavior configurable?
For the existing behaviour, a work-around was provided by @SgtSilvio here.
The text was updated successfully, but these errors were encountered:
No branches or pull requests
馃殌 Feature Request
Currently, when using
automaticReconnectWithDefaultConfig, the client may hang indefinitely if it can't reconnect to the broker.As pointed out (and requested by @dowhiletrue in #302), users would like the ability to configure this behavior to either:
馃攬 Motivation
馃洶 Alternatives
For the existing behaviour, a work-around was provided by @SgtSilvio here.
馃搸 Additional context
The text was updated successfully, but these errors were encountered: