On Tue, Dec 2, 2008 at 3:08 PM, Amir Michail <[EMAIL PROTECTED]> wrote: > > Hi, > > When doing a urlfetch, it may take quite a long time. As this is not > a CPU usage issue, what's the point of limiting the request time > anyway? Why not allow the request to go on for a minute or so?
As I understand it, the thread doing the fetch will be blocked and cannot service any other requests until it finishes the fetch. Now, if a lot of threads are blocked waiting for that resource to be fetched, you will not be able to scale -- as it would be effectively an inadvertent denial of service for your app (and the whole infrastructure). -- JM Ibanez -- The worst government is often the most moral. One composed of cynics is often very tolerant and humane. But when fanatics are on top there is no limit to oppression. -- H. L. Mencken ----- http://www.livejournal.com/~jmibanez/ http://www.mycgiserver.com/~butiki/ --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---