On Mon, Oct 24, 2011 at 10:34 AM, Gerald Tan <[email protected]> wrote:
> There are two methods I can think of. > 1) Copy on Write Entities - persist a new copy of the entity each time you > want to update it, together with the timestamp it is written. When you want > to retrieve the entity, query for the latest version. > The eventual nature of queries in the HRD will sometimes give you stale versions. > 2) Use a backend instance to store the entities into the backend instance > memory. This is the best answer if you have anything approaching a realtime game. Turn-based games can usually be made to work in the datastore, but if you expect a lot of rapidly changing shared state, cache it in memory and sync it to the datastore at intervals. Jeff -- 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.
