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: google-appengine@googlegroups.com [mailto:google-appengine@googlegroups.com] On Behalf Of PK Sent: Tuesday, October 04, 2011 2:11 AM To: google-appengine@googlegroups.com 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 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. -- 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.
