Add cluster support via Resolver #156
Closed
Conversation
This file contains 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
nemith
force-pushed
the
cluster
branch
2 times, most recently
from
3d0ef11
to
c77830d
Compare
|
I went ahead and wrote my own wrapper that has this and does things slightly different. No longer have a strong requirement for this. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This adds support for RabbitMQ clusters to connect up to one of a number of servers.
It does this through a
Resolverinterface which has a single method calledResolve()which can return a list of servers. There is a standard implementation included calledStaticResolverthat will just take a list of URLS to connect to and optionally shuffle that list.This interface approach allows for implementers of the library to extend for service discovery or other advanced typologies.
Fixes: #148