Async commands are executed in order. TCP is ordered, as you say,
and it is possible to send multiple commands without waiting for
a response. This is called pipelining. MULTI-EXEC with pipelining
is a good idea. It is efficient. From
> (...) starting with Redis 2.6.5, the server will remember that
> there was an error during the accumulation of commands, and
> will refuse to execute the transaction returning also an error
> during EXEC, and discarding the transaction automatically.
> Before Redis 2.6.5 the behavior was to execute the transaction
> with just the subset of commands queued successfully in case
> the client called EXEC regardless of previous errors. The new
> behavior makes it much more simple to mix transactions with
> pipelining, so that the whole transaction can be sent at once,
> reading all the replies later at once.
There is no mention of out-of-order commands in the hiredis
README or in the Redis documentation. The information you found
seems wrong or at least very outdated.
> You received this message because you are subscribed to the Google
> Groups "Redis DB" group.
> To unsubscribe from this group and stop receiving emails from it, send
> an email to redis-db+u...@googlegroups.com
> To view this discussion on the web visit