memcache delete doesn't work

[theo]

Has anyone else noticed that memcache.delete() doesn't work? Am I
totally off my rocker?

I talked with a friend who is experienced in using memcache and he
couldn't figure it out, so I posted a bug report:

http://code.google.com/p/googleappengine/issues/detail?id=623&can=5&colspec=ID%20Type%20Status%20Priority%20Stars%20Owner%20Summary#makechanges

This isn't super serious, as I can just use memcache.set(,None),
although it's not nearly as nice.

[David Symonds]

On Tue, Aug 12, 2008 at 9:13 PM, theo <theodore....@gmail.com> wrote:

> Has anyone else noticed that memcache.delete() doesn't work? Am I
> totally off my rocker?

I think you might be a bit off your rocker. memcache is not
appropriate as a synchronisation mechanism, since it's a cache, not a
guaranteed storage. I really wouldn't be surprised if the first .add()
and .delete() calls only takes effect at the end of the query, which
would explain why the second .add() apparently fails.

If you want a global locking mechanism (really bad for scalability, so
avoid if you can!) then use the datastore itself.

Dave.