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

Be able to use one connection for multiple producer/consumer #61

Open
MarcAntoine-Arnaud opened this issue Mar 24, 2024 · 1 comment
Open
Labels
enhancement New feature or request

Comments

@MarcAntoine-Arnaud
Copy link

Hi,

Thank you for this crate and job made !

I wanna to know if a reason exists to didn't have more attributes on QueueBuilder to pass queue parameters.
Based on that we can une one connection with multiple queues.

Or do you see another way to address that ?

Best,
Marc-Antoine

@svix-jplatte
Copy link
Member

Yeah, this isn't currently possible. I'm thinking the best solution would be to allow users to pass in a connection pool instead of an address (but keep the address-based initialization as a convenience). This runs a bit counter to another goal of decoupling the public API from other crates like redis, but the best fix for that might be to split omniqueue into multiple independent crates anyways: one base crate for the traits, dynamic dispatch and such and one crate per backend like omniqueue-redis (which would then be the only crate to need a release when doing an upgrade of the redis dependency).

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

No branches or pull requests

2 participants