Skip to content
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

Use separate connections for producers, consumers, etc. #174

Open
rnowling-memphis opened this issue Jul 8, 2023 · 0 comments
Open

Use separate connections for producers, consumers, etc. #174

rnowling-memphis opened this issue Jul 8, 2023 · 0 comments
Assignees
Labels
Feature Request New feature or request

Comments

@rnowling-memphis
Copy link
Contributor

Currently, producers and consumers all share a single connection to the Memphis broker. The user creates a Memphis object and calls connect() to establish a connection. When producers and consumers are created with Memphis.producer() and Memphis.consumer(), the connection object is passed to the constructors of the Producer and Consumer classes.

Should we be doing this? Or should each new producer or consumer get its own connection?

@rnowling-memphis rnowling-memphis self-assigned this Jul 28, 2023
@rnowling-memphis rnowling-memphis added the Feature Request New feature or request label Jul 28, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Feature Request New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant