On Dec 1, 8:15 pm, "Andrew Badera" <[EMAIL PROTECTED]> wrote: > The timeout I see as more of a GAE issue, not a Twitter one. You get what > you pay for, on both sides of that equation.
It's not a CPU usage issue in the GAE. It's just that the request to the twitter search API takes too long and urlfetch times out in the GAE. Hopefully a timeout parameter will be added to urlfetch soon... Amir > > No SLA, no billing from Twitter, beta and no billing on GAE's part ... and I > think we can agree, GAE hasn't been particular forthcoming nor cooperative > about what constitutes a true mcycle or a long-running request. > > That said, perhaps there's some optimization to be done on OR ... > > Thanks- > - Andy Badera > - [EMAIL PROTECTED] > - (518) 641-1280 > > -http://higherefficiency.net/ > -http://changeroundup.com/ > > -http://flipbitsnotburgers.blogspot.com/ > -http://andrew.badera.us/ > > - Google me:http://www.google.com/search?q=andrew+badera > > On Mon, Dec 1, 2008 at 8:10 PM, Amir Michail <[EMAIL PROTECTED]> wrote: > > > Hi, > > > OR search queries can take a long time and are causing lots of > > timeouts with google app engine. > > > Amir
