I've extended my implementation of a sharded, memcached counter to allow more graceful handling of failed shard puts because of timeout, capability disabling, etc. The idea is to use memcache as a buffer for failed put data, which gets re-added to the next successful put.
Longer writeup here: http://billkatz.com/2008/10/Fault-tolerant-counters-for-App-Engine Code is here: http://github.com/DocSavage/sharded_counter/tree/master/counter.py Let me know if you see holes in this approach. There might be a way to generalize this method to provide a more fault-tolerant datastore layer for more sophisticated models. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Google App Engine" group. To post to this group, send email to google-appengine@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en -~----------~----~----~----~------~----~------~--~---
