Just a related thought, this kind of thing should be a non-issue once the background processes api is released which should be soon. Long running processes should probably be migrated to that once it's released rather than using cron since you're not limited to how often cron runs.
On Mon, Jun 8, 2009 at 3:35 AM, Wooble <[email protected]> wrote: > > No, urlfetch works in in a cron job. You just can't try to redirect > the "browser" that's visiting your site to run the cron job. > > On Jun 6, 3:47 pm, Alain de R <[email protected]> wrote: > > does this mean that I cannot use urlFetch in a cron job ? > > > > On Apr 16, 10:05 pm, Anthony Baxter <[email protected]> wrote: > > > > > You can't use 302 redirects to extend a cron jobs lifetime, sorry. > > > > > Anthony > > > > > On Apr 17, 11:48 am, Ben <[email protected]> wrote: > > > > > > So trying outcron, I use a outside box tocrontoday and I use the > > > > common App Engine 302 method to avoid deadline exceeded errors (hand > > > > to another script via 302 for each item rather than trying to do all > > > > in one shot). When I move my job over to App EnginecronI get "too > > > > many continues" can someone tell me how many 302s it will follow and > > > > assuming it is relatively limited do I have any options here? > > > > > > Thanks, > > > > -Ben > > > > > > > -- ======================================= 株式会社ビープラウド イアン・ルイス 〒150-0012 東京都渋谷区広尾1-11-2アイオス広尾ビル604 email: [email protected] TEL：03-5795-2707 FAX：03-5795-2708 http://www.beproud.jp/ ======================================= --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
