Hi Tim, Thanks for your hindsight. I think I'll first try and play with tasks queues and see how it goes, and then study how to integrate a backend later on when I'm more familiar with all of this.
Thanks again :) -- Sébastien Tromp On Wed, Aug 10, 2011 at 12:34 PM, Tim Hoffman <[email protected]> wrote: > Hi Sébastien > > Off the top of my head > > The resident backend could maintain its own wall clock time, and sit in a > busy loop checking for actions to perform via memcache. > It could then put updates back into memcache, the front ends can be keeping > an eye on the gamestate updates in memcache (tasks maybe, or the backend > could signal front ends via xmpp) > > Just some thoughts. > > 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/-/1Ln8GBqXiucJ. > > 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. > -- 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.
