For some reason I can't see your answers here Tim and Ikay. You raised some good points.
Tim, if I'll use your basic pattern: *Check in memcache * *if not their fetch from the datastore* *if you think the data will be re-used stick it in memcache* then I don't see any reason to use memcache directly, instead I'll use objectify (or something similar), makes sense ? Correct me if I'm wrong but fetching from the datastore is not the problem, writing to it is heavier, so making my queries faster probably will not ease my problems. Let's say I can ease my assumptions, say that whenever I update the client if it doesn't fetch the information in X seconds then I'm willing to remove the item from cache and move it to the datastore, in case the data fetched then there is no need to store it at all (it is cached in the client). Is there a way to implement such a behavior ? Thanks for your help guys. -- 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/-/H7y_FWpeY5AJ. 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.
