Hello, The past several planned and unplanned outages where the datastore has been readonly, has also had the memcache made unavailable for at least part of the duration.
I'd been working on the python session class, expanding it to allow for periods where the datastore was read only, but memcache is available. The point being that applications that could persist in a read only state would also be able to keep user state or whatever else they were using sessions for. Except for gracefully getting past datastore timeout issues, this extra complexity doesn't seem to be solving much for any of the downtimes though. So I'm just curious how tightly integrated the write functionality is for both? --~--~---------~--~----~------------~-------~--~----~ 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 google-appengine+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en -~----------~----~----~----~------~----~------~--~---
