Thanks for the pointer. I read the documentation on back-end, and it looks like an alternative to handling the tasks in the App Engine standard application, but still keeping the task queue to provide a timer-like feature. Is that correct?
The pros of a backend would indeed be the ability to store more in-memory information to maintain the game state. The only limitation I am seeing now is the current impossibility<http://groups.google.com/group/google-appengine/browse_thread/thread/f7fe4a5ed266a9ca> to use the same channel between front-end and back-end. Which would mean, once my task has been processed, that I need to find a way to communicate the change in the game state to all the other players. Is there a way to do this? Thanks again for your help :) -- Sébastien Tromp On Wed, Aug 10, 2011 at 11:58 AM, Tim Hoffman <[email protected]> wrote: > Hi > > You probably want to have a look at a resident backend. > > > http://code.google.com/appengine/docs/python/config/backends.html#Types_of_Backends > > These could provide the facilities you need to maintain > a continuous game state and establish an in game time. It could then Pull > tasks > or get messages direct from the datastore. > > 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/-/lFgRyRBonNYJ. > 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.
