On Wed, Oct 8, 2008 at 6:00 PM, Alexander Kojevnikov <[EMAIL PROTECTED]> wrote: > > Star this issue: > http://code.google.com/p/googleappengine/issues/detail?id=6 > > Google mentioned on one of the conferences that they are working on > this, but no timeline was given.
What's important in what I propose is that you do not need to worry about resource issues and the handler is written exactly as with any other handler. Google decides when your handler runs and whether to interrupt it a few times to avoid you going over quota. Amir > > On Oct 9, 8:42 am, Amir Michail <[EMAIL PROTECTED]> wrote: >> Hi, >> >> Why not handle resource intensive requests in a transparent way? This >> can be done without changing quotas/deadlines. >> >> In particular, you could give developers a way to designate certain >> request handlers as potentially resource expensive. >> >> You could then run these handlers on our behalf at your convenience. >> It's ok for them to take a long time to complete. However, it would >> be nice to inform us when they do complete (e.g., by email). >> >> The point is that the code for such handlers would be the same as the >> code for normal handlers. There's no need to split up the task, >> invoke the handler repeatedly, etc.. You could do that automatically >> for us behind the scenes. >> >> Amir > > > -- http://chatbotgame.com http://numbrosia.com http://twitter.com/amichail --~--~---------~--~----~------------~-------~--~----~ 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 [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en -~----------~----~----~----~------~----~------~--~---
