mdelete and Cache::Memcached::delete_multi()

[Dustin Sallings]

On Nov 15, 2007, at 10:29 , dormando wrote:

> With noreply you can still end up doing:
>
> set blah 0 0 2
> hi
> set another 0 0 3 noreply
> bye
> set more 0 0 3
> foo
>
> ... then when you read, did the error come from the first or third  
> set?
>
> ... 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.

-- 
Dustin Sallings