CAS operation

[Chris Goffinet]

Agreed.

Does "gets" only assign when called at that point the 64 bit unique  
value, or are you setting every object that is cache a unique  
identifier?

Is your prototype in python or patched diff against trunk?


Chris Goffinet
goffinet at yahoo-inc.com



On Sep 8, 2007, at 1:12 AM, Dustin Sallings wrote:

>
> On Sep 8, 2007, at 1:07, Chris Goffinet wrote:
>
>> So with every object having a 64 bit unique value, if I call gets,  
>> I retrieve a value for the object (unique value), then send  
>> memcache this old value (64 bit unique), new value (new update of  
>> object) and if the unique is still the same for object, it will  
>> push the change?
>
> 	Right, that's the idea.  Otherwise, it'll tell you that the key has  
> expired (or otherwise gone missing) or that it's changed since you  
> last looked at it.
>
> 	gets gives you both the value and the value identifier at the same  
> time (otherwise, there wouldn't be much of a point).
>
> 	The regular get operation(s) could potentially return the same  
> thing, but it would require protocol extensions that may confuse  
> clients in the ascii protocol, and would definitely do so in the  
> binary protocol.
>
> -- 
> Dustin Sallings
>
>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.danga.com/pipermail/memcached/attachments/20070908/fc4458d7/attachment.htm