The request deadline is actually 30 seconds now, but yeah, as far as I can tell cron jobs are just intended to free you from needing a cron job on your own machine to hit a URL with wget or whatever periodically.
Long-running processes are probably what you're looking for; hopefully we'll see them soon. In the meantime, the remote API might be the best solution for big database cleanup jobs. On Apr 12, 11:41 pm, jorge <jorge.velazq...@gmail.com> wrote: > I guess I probably misunderstood and thought that cron jobs weren't > subject to the same 10 second request deadline for HTTP requests? I'm > trying to run a cron job that sends out a mailer. Unfortunately, it's > taking longer than 10 seconds so the job will fail about halfway > through. I guess I could rewrite it to only do batches at a time. > The means extra tables in my database to keep track of who has been > mailed, etc. Not a big deal, I guess. It just seems that this > restriction makes cron jobs fairly limited in what they can do. A > database cleanup job, for example, is going to take longer and longer > as tables grow and will almost certainly always hit this limit, and > create a situation where the cron scripts will have to be rewritten > and additional tables written to manage intermediate state, etc. > > Is the intent that the cron jobs will remain subject to the same > restrictions as other requests? --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Google App Engine" group. To post to this group, send email to google-appengine@googlegroups.com To unsubscribe from this group, send email to google-appengine+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en -~----------~----~----~----~------~----~------~--~---
