Hello, I am building a multiplayer game whose play sessions are rather short (around 5 mins). Everytime a player sends their move, it updates the game state in the cache. Since the cache is unreliable, I then update the datastore with the updated data. My concern is there will likely be many useless datastore updates - meaning two consecutive persistence calls while the data still is in the memcache.
I was thus wondering whether you had any suggestion about this. I was thinking of listeners that would be called when the data is about to be evicted from the cache, who would be the one to do the actual persistence. But from what I read<http://code.google.com/appengine/docs/java/memcache/usingjcache.html#Features_Not_Supported> this is not possible today. Has any one of you run into a similar requirement? How have you coped with it? -- Sébastien Tromp -- You received this message because you are subscribed to the Google Groups "Google App Engine for Java" group. To post to this group, send email to google-appengine-java@googlegroups.com. To unsubscribe from this group, send email to google-appengine-java+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-appengine-java?hl=en.
