-
Notifications
You must be signed in to change notification settings - Fork 447
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
[Feature Request] Pipeline coroutine safety #278
Comments
In the current implementation, the underlay connection and the |
or we can block the connection only when committing the pipeline, and let the user decide whether to create another connection? |
What do you mean by "block the connection only when committing the pipeline"? |
Instead of creating a new connection, we lock the connection until the pipeline finishes |
IMHO, it would make thing complex if we put the connection management inside the redis client. |
I agree. I'm now using a strategy to clone if the connection is doing a pipeline. |
When using a pipeline combined with a coroutine, some commands might get mixed into the pipeline. Please consider introducing pipeline objects, e.g.:
The text was updated successfully, but these errors were encountered: