-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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
Stream with Block parameter #1158
Comments
This is deliberate; see this paragraph: https://stackexchange.github.io/StackExchange.Redis/PipelinesMultiplexers.html#multiplexing We're aware that people want this option - it needs some internal work to make it supportable, however. Additional links: |
Not sure why it was closed
|
Literally everything in my previous reply is saying why it is closed. Until we ship a pool-based, rather than multiplexed, core (or more likely: a dual core that allows you to use pool-based mechanisms), this isn't viable. |
Got you, thanks |
How can I run XRead with block parameter with code? I am trying to replace pub/sub with the stream data type so that our clients don't lose messages. Is it intentionally not supported by the driver?
Xread BLOCK 100 STREAMS channel1 $
Thanks,
Hitesh
The text was updated successfully, but these errors were encountered: