Won't you have problems with instances that live around the time you update content?
When you send the update request, that instance will update it's dict (and memcache and the datastore). If you have another instance alive at that time, it won't know about the update and will continue serving the old one. If your update happens at a predictable time you could make the cache logic reload from the datastore, but for unpredictable updates this technique will break if your app scales above one instance. -- 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.
