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

Add sipport for Pipelining #42

Open
GoogleCodeExporter opened this issue Nov 3, 2015 · 0 comments
Open

Add sipport for Pipelining #42

GoogleCodeExporter opened this issue Nov 3, 2015 · 0 comments

Comments

@GoogleCodeExporter
Copy link

A Request/Response server can be implemented so that it is able to process new 
requests even if the client didn't already read the old responses. This way it 
is possible to send multiple commands to the server without waiting for the 
replies at all, and finally read the replies in a single step.
Redis supports pipelining since the very early days, so whatever version you 
are running, you can use pipelining with Redis.

There should be something like the batch request, which remembers the order of 
commands and places the results in accordance with this order.

Original issue reported on code.google.com by [email protected] on 14 Jan 2012 at 3:55

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant