Yes the 30 seconds applies everywhere You should use a task queue, and submit multiple tasks for instance once for each URL you wish to fetch, process the result and either add a new task in an hours time if successful, or resubmit the task to run in a few minutes if the request failed.
That way you are not directly limited by what you can do in any single request handler. T On Sep 9, 9:43 am, Locke <[email protected]> wrote: > http://code.google.com/appengine/docs/java/runtime.html > "A request handler has a limited amount of time to generate and return > a response to a request, typically around 30 seconds. Once the > deadline has been reached, the request handler is interrupted." > > I'm writing an app that will, every hour, make multiple URLFetch > requests to various external servers. These servers may take several > seconds each to respond to the requests (this is not under my > control). > > I understand that app engine kills your process with an HTTP 5XX if > you leave the user waiting for more than 30 seconds. That's fine; most > users will quit after 10 seconds anyway. But what about processes > called by cron? They aren't interactive--there is no reason to worry > about making a user wait. Are cron jobs crippled by the same limit? I > hope not; it would be a shame if App Engine couldn't "scale" to the > size of an app that makes just three URLFetch calls, should those > remote servers impart 10-second delays. > > So does the 30 second rule apply to cron process? If so, is there any > work-around? > > Thanks in advance. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
