Yes, the task-queue is also limited to 30 seconds. Longer running jobs are on the roadmap (http://code.google.com/appengine/docs/roadmap.html).
The task queue is ''better'' than user requests when the request needs run multiple times to complete some processing, unless you client knows it needs to keep re-requesting. Of course in many cases a batch of tasks are initiated by a user request. Also, if a process takes a long time to run it should be in a task; otherwise your app may not get additional instances spun-up. I think it would be better to push the work from your render farm on EC2 to GAE when it is completed. Otherwise you will need to poll to find updates. Of course, if you only need updates once per hour polling is much less of a concern. Robert On Sun, Oct 24, 2010 at 09:37, Maxim Veksler <[email protected]> wrote: > Hello, > Sorry for the basic question, can't find any clear answer on the subject. > Is the task queue API in any way better for long term running jobs then a > simple request to a defined "notfityUpdate" interface being called by our > processing farm? > While at it, what it the most recommended method for pushing data from the > rendering farm, sitting on EC2 to GAE datastore? > The GAE application is java if that plays any role, but don't let that stop > you. > Thanks, > Maxim. > > -- > 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. > -- 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.
