kroki wrote:
On Oct 29, 3:47 pm, Trond Norbye <[email protected]> wrote:
I think it is a lot better that the server
sends back an error message and let the client handle that instead.
Handle... how? What are your suggestions on how to support this in
clients?
Clients should always be able to receive error messages. This specific
problem is a bit tough, because you send an invalid command to the
server and believes that it is a legal command you shouldn't receive any
output from, so you will most likely not see the error before you
execute the next command you expect a response to. With the ASCII
protocoll you cannot map the error back to the command causing the
error, but that problem is addressed in the binary protocol (the error
packet contains the command opcode and the opaque field).
This specific problem is something you should discover when you run your
test suite towards the new server to before deploying it.
Cheers,
Trond
