Set rpc client connexion to be lazy #185
Merged
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
Contributor
|
Yeah! |
videlalvaro
added a commit
that referenced
this pull request
Jun 20, 2014
Set rpc client connexion to be lazy
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 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.
Actually, each time a rpc client service with rabbitmq is construct, a connexion to RabbitMqServer is launched as the extension add a method call to initClient in the container.
Sometimes the rpc client is loaded but not used (for our case we use it in the security context but if user is anonymous we never make a call to rpc)
This is a BC break for people using this class with the queuename member as it's no longer protected (user should use getQueueName function instead of the queuename variable)