mdelete and Cache::Memcached::delete_multi()
dustin at spy.net
Thu Nov 15 19:05:26 UTC 2007
On Nov 15, 2007, at 10:29 , dormando wrote:
> With noreply you can still end up doing:
> set blah 0 0 2
> set another 0 0 3 noreply
> set more 0 0 3
> ... then when you read, did the error come from the first or third
> ... and with silent, single-threaded clients need to ensure they
> don't inject another thread's commands in the middle of an altered
> connection's state.
This is a good argument for client opaque.
More information about the memcached