On Nov 25, 2008, at 7:52 PM, Dustin wrote:
On Nov 25, 6:07 am, Trond Norbye <[EMAIL PROTECTED]> wrote:
I'm not sure if this is really possible with the binary protocol,
because we create the cas when we store the item and the cas is
returned in the response. We also return cas in every get, so there
is
basically no way we can delay the creation of a cas until the user
actually wants it.
If an object has CAS disabled, you either:
a) Always return 0 and always mutate it.
b) Return a value you won't accept.
b kind of sounds better to me. The idea of ``enabling'' CAS for an
object is something similar to append, I'd imagine.
Ok, so I went ahead with my ideas before I read your email, and pushed
a version to my github repository:
http://github.com/trondn/memcached/commit/ce8da7c143c21e14a7a47d373e0b6e497429efad
If you start memcached with -C it will not generate CAS, and always
return 0 as the cas value..
Dustin: I cloned your repos, and pushed it.. hope I did it the right
way?
Cheers,
Trond
