Hi You care correct, writing is the costly component. Doing a get by key is normally veru quick.,
>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 ? I don't think this is correct. You would always write to the datastore and then cache. If you stick it in memcache and plan on persisting it in the datastore later you may well lose data. It might help to think about your writes and processing as seperate phases. Write raw data, then use a task or perspective search to aggregate and prepare the data for the client, then notify. Rgds T -- 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/-/_Js7h79-ulUJ. 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.
