On Apr 6, 7:21 am, X <wangx0...@gmail.com> wrote: > There seems to be a protocol issue with the noreply option. Eor > example, if you issue two "SET" and receive one "ERROR" back, how do > you know which SET failed and how does a client handle that "ERROR" > message?
This is unfortunate, but that's the way it was designed. I don't support it in my client for that reason. We did fix this in the binary protocol -- you can have commands that don't respond to "normal" conditions allowing you to only receive exceptional conditions.
