Added ability to specify multiple hosts to connect to #52
+55
−11
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Populating the "hosts" config option with a list of {Host, Tuple} pairs
will cause emqttc to attempt to connect to each host in the list
before initiating the reconnect strategy.
If not a response of false is returned.
If it is connected a response of {true, {Host, Port}} is returned.
…er during init. That way the connect function does not need to check whether hosts is empty but can simply pull hosts out of it for connecting. It is guaranteed to always have at least one entry because if it is not explicitly defined then it have the "host" and "port" state members added to it which will always be defined.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
5 participants
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.
Added the ability to specify a list of of host and port tuples of brokers to connect to. Each host in the list will be attempted before the reconnect strategy is engaged.
Also added an "is_connected" api function that returns false if not connected and {true, {Host, Port}} when connected.