That would work up until your data got evicted at the wrong time... Though this gets me thinking: it would be really, really nice for many applications to have a *guaranteed* memcached-style in-memory table that you could use to share data between instances (and between FE/BE). Unlike memcached there would be no automatic management; instead you would manually add/remove items to stay within a hard limit (or put()s would fail). The hard limit could depend on configuration and maybe you could pay for more if you needed it.
- Kris On Thursday, August 9, 2012 7:38:40 AM UTC-7, Hernan Liendo wrote: > > * > On the other hand, I think you could simplify a little your scoring > solution. What if you hold user’s scores on sharded MemCache entries and > after a while you get all of them and save the result on the DataStore?* > > -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To view this discussion on the web visit https://groups.google.com/d/msg/google-appengine/-/3V5Fp6ul8dsJ. 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.
