there are sessions managers that read directly from datastore only-if memcache isn't there. think of memcache as "data stored in RAM that you can hopefully still read, which is faster and cheaper than reading from datastore again" sometimes there are new stuff on the memcache API, be sure to keep track of the news (this is from the latest sdk version: http://googleappengine.blogspot.com/2011/08/app-engine-153-sdk-released.html )
On Aug 25, 7:26 am, Per <[email protected]> wrote: > Actually, forget it, my mistake. I think I was simply not catching > enough exceptions while putting stuff into the memcache. Obviously, > you should never reply on the memcache being there at all, and just go > to the datastore instead. Must drink more coffee before posting. > Sorry about that! > > Per -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To post to this group, send email to [email protected]. 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.
