On Wed, Aug 17, 2011 at 11:16 PM, Robert Kluin <[email protected]> wrote: > > Yeah, exactly. There are several other variations on the same theme > too. If you were to use long-running tasks or cron-jobs for this you > might need some type of locks or guards in case two run at the same > time. A backend should simplify the process quite a bit since a > process can run for a very long time (24 hours) and you can crank up > the memory; the downside is that backends extremely expensive and they > won't be able to scale as wide as a task-based method.
Thanks a lot for all your help. I'll first validate the concept using Crons. It will allow me to test everything with no or little cost in a first time. And given that the application is for now in a prototype phase with little traffic, I think the risk of locking is rather low. If this go well, I'll look into using a backend, and how to handle communication between backend and frontend (Tim suggested XMPP, but from what I saw in the documentation it is not possible to directly communicate with the frontend). Thanks again :) -- Sébastien Tromp -- 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.
