We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
A single consumer cannot read from a pattern and a normal topic. So at least 2 consumers must be created. This can be done internally, no problem here.
Now... how should the interface look?
async with broadcast.subscribe(channel="logs/*") as subscriber:
If we want to use the current channel parameter, then a Consumer should be created each time .subscribe is called (if not mistaken).
channel
.subscribe
async with broadcast.subscribe(pattern="logs/*") as subscriber:
In this case we can have 2 consumers only, but we'd have a pattern keyword which may not be supported by every backend.
pattern
The text was updated successfully, but these errors were encountered:
API matches up with what I'd expect, yup.
Sorry, something went wrong.
No branches or pull requests
A single consumer cannot read from a pattern and a normal topic.
So at least 2 consumers must be created. This can be done internally, no problem here.
Now... how should the interface look?
If we want to use the current
channel
parameter, then a Consumer should be created eachtime
.subscribe
is called (if not mistaken).In this case we can have 2 consumers only, but we'd have a
pattern
keywordwhich may not be supported by every backend.
The text was updated successfully, but these errors were encountered: