Brandon, Who asked for a promise? I asked for an answer to a very reasonable question. Some guidance on why they picked 10 seconds in the first place and that they are considering changing it for this or next release would have been more than enough. The fact that 4 days later they changed it means that they have been thinking about it for some time.
Java already has multithreading and when MT comes to python the instance time issue you are raising will be no issue. While the thread sleeps waiting for the urlfetch to complete other threads will make use of the instance. PK PS regarding the "you get mad" language you probably confuse me with somebody else or you have not seen somebody being really mad. If you try a bit harder with this kind of language and attitude you might make me mad but I doubt it :-) On Oct 4, 2011, at 2:18 AM, Brandon Wirtz wrote: > If they promise, then cut it, you get mad. If they don’t promise and deliver > you get mad. > > What was the right solution? > > Generally I think this support was added to make things like Pay Pal work, > but you need to be careful using it, waiting 58 seconds for your URLFetch > will burn a lot of instance time. > > > From: [email protected] > [mailto:[email protected]] On Behalf Of PK > Sent: Tuesday, October 04, 2011 2:11 AM > To: [email protected] > Subject: Re: [google-appengine] Re: urlfetch maximum interactive timeout why > 10 seconds and not 20? > > The 1.5.5 pre-release that was just announced today includes: > > " We have increased the URLFetch maximum deadline from 10 seconds to 60 > seconds." > > So I am thinking: I posted this topic four days ago. I gave it two days to > see somebody from Google reply that they will do it or that they will never > do it or something. Then I spent a night working around the issue. I am > wondering: Couldn't somebody from Google reply to this thread and mention > that this will be coming in the next release??????? > > PK > www.gae123.com > -- > You received this message because you are subscribed to the Google Groups > "Google App Engine" group. > To view this discussion on the web visit > https://groups.google.com/d/msg/google-appengine/-/vQMX34ZWUb8J. > 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. > > -- > 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. -- 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.
