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.

Sign up for GitHub

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

Jump to bottom

The binary protocol does not implement noreply for the storage commands #11

Closed

GoogleCodeExporter opened this issue Nov 9, 2015 · 1 comment

Labels

auto-migrated Priority-Medium Type-Defect

GoogleCodeExporter commented Nov 9, 2015

It is not possible to issue a storage command without expecting a message
back (the noreply flag in the textual protocol).

we should create q versions like we did for get.

Original issue reported on code.google.com by trond.no...@gmail.com on 20 Jan 2009 at 10:46

The text was updated successfully, but these errors were encountered:

Author

GoogleCodeExporter commented Nov 9, 2015

Fixed in: 
http://github.com/trondn/memcached/commit/37253eb3eddd115098d86daf8ea77694297711
55
and 
http://github.com/trondn/memcached/commit/458b6c2acc97b413321b73c8238fd1eb43c995
b4

Original comment by trond.no...@gmail.com on 20 Jan 2009 at 2:31

Changed state: Fixed

GoogleCodeExporter added Priority-Medium auto-migrated Type-Defect labels

GoogleCodeExporter closed this as completed

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