Implement Reusable RabbitMQ Connection in Publisher #46
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
radwo
changed the title
radwo
changed the title
Closed
| routing_key: "test-messages", | ||
| } | ||
|
|
||
| Tackle.publish("Hi!", options) |
Collaborator
There was a problem hiding this comment.
Can you add a test that verifies this? It should probably publish a few times in a row and check the number of open connections.
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 pull request introduces enhancements to the
Tackle.publishby implementing the ability to reuse a RabbitMQ connection viaTackle.Connection.open(name, ..). This change aims to improve performance and resource management by minimizing the overhead of establishing new connections for each publishing action.