This repository has been archived by the owner on Jul 12, 2023. It is now read-only.
Refactoring and indefinite reconnect (v1.0.0) #14
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Somewhat larger realtime factoring plus improvements to support more graceful error handling and indefinite reconnecting
A highlight of realtime client changes include
on_msg
->on_message
). This is a breaking change and the main reason for a major version update.MqttError
class that will wrap MQTT related exceptions, and make sure these exceptions are thrown in failure instances as opposed to suppressing themconnect_and_subscribe
to be callable multiple timesconnect_and_subscribe_forever
as a wrapper aroundconnect_and_subscribe
which will attempt to auto-recover from any disconnections with an exponential back-off strategyconnected
future which will trigger whenon_connect
is called. This allows us to do a timeout wait and detect when connection is never achieved.Plus some changes to development