I use it for accurate statistics display.
Basically I have a counter of a certain kind of entities.
Whenenever I create more of them I update the counter.
The atomic action guarantees accurate statiscs for when I should
create multiple entities concurrently.
The fact that it can be sometimes wiped
The methods come from the original memcached implementation that App
Engine's memcache copies. I think they wanted people to be able to port
code that uses memcached without having to handle missing methods.
Judging from Brett Slatkin's Google I/O talk about PubSubHubbub it sounds
like while m
These are one of the most useful primitives. I use incr() for keeping
sequence numbers in a multiplayer game. Works pretty well. As everything in
memcache you have to deal with occasional "evaporation"
--
You received this message because you are subscribed to the Google Groups
"Google App Eng
Strom, your use of memcache incr and decr is a great example:
Synchronise a memcache counter with the count() of a datastore entity query.
I imagine it could be tricky to *exactly* synchronise the memcache counter
with the datastore if the memcache counter did get purged.
Calvin, I had a look a
