You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This is just a question. I'm new to node redis and I'm reading the source code and find the command are send by socket one by one in order. But if then the reply is also keeps the order? i.e. 1st execute -> 1st reply, 2nd execute -> 2nd reply
The text was updated successfully, but these errors were encountered:
The order is always respected with some very minor exceptions. The exceptions are (I expect you fire a command sync before the following mentioned commands):
you use client.batch().exec() or client.multi().exec_atomic() (missing commands)
you pass wrong types to the pass argument in client.auth(pass, [callback])
you fire a command after you closed the connection using client.quit
Those should be all exceptions.
In those cases the result for the mentioned commands are returned async but the return value is handled by the client itself right away and therefor the execution order will not be the same. It is possible to handle those return values in order too but I have to think about it further at some point, since the solution that came to my mind would have a minor performance penalty and I do not see a real need to guarantee the execution order in those cases too.
This is just a question. I'm new to node redis and I'm reading the source code and find the command are send by socket one by one in order. But if then the reply is also keeps the order? i.e. 1st execute -> 1st reply, 2nd execute -> 2nd reply
The text was updated successfully, but these errors were encountered: