Skip to content

feat: allow user to define client provided name #344

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Mar 5, 2022

Conversation

sarmis
Copy link
Contributor

@sarmis sarmis commented Mar 5, 2022

In some cases, it is useful to provide a way for the application to give a meaningful name to the rabbit connection in order to be able to reason about existing connections on a rabbit server when there are multiple connections.

@catcherwong catcherwong self-requested a review March 5, 2022 07:04
Copy link
Member

@catcherwong catcherwong left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants