Thanks Adam! That makes sense to me - I believe Redis transactions are
atomic by default so the `cas` method wouldn't apply there. I took a look
at the LocMemCache code, and I think that the need for cas in this instance
also doesn't exist - because the code uses a threading Lock() to prevent
r
pymemcache also supports a cas() method, so that's two backends that could
have the other method.
I think the main problem is as Russell highlighted - supporting other
backends. It would be nice to see research into emulating cas(), at least
on LocMemCache which is often used as a fake during test
Is it CAS specifically that you want? Or a Locking primitive? Or some
other operation?
--
Curtis
On 18 January 2014 12:45, Russell Keith-Magee wrote:
>
> I can't see any reason that we *shouldn't* support it - it seems like a
> reasonable primitive to support.
>
> The only real issue is ensur
I can't see any reason that we *shouldn't* support it - it seems like a
reasonable primitive to support.
The only real issue is ensuring it either is, or can be, implemented on all
backends and supported memcache libraries. If you can produce a patch that
does this, I'd say it has a good chance of
Hi all,
there is a usefull (for me now :)) CAS operation in memcache:
http://neopythonic.blogspot.ru/2011/08/compare-and-set-in-memcache.html,
but I can't find it in django cache api.
Are there any reasons for it not to be implemented there?
Thank you!
--
You received this message because you a
