Hi there,
We had a bunch of trouble yesterday with slow and timed out
queries, so if you saw more than expected yesterday that was a known
issue. In the normal case lowering the rpp value will make things
timeout less often. Since search is optimized for normal queries and
not user timelines you may also want to look at using the twitter.com/
statuses/user_timeline for the user and match the phrase yourself.
Twiter.com has been optimized for serving by-user timelines so that
usually much faster and less likely to timeout. The extra coding
should payoff in reliability.
Thanks;
— Matt Sanford / @mzsanford
On Jan 29, 2009, at 09:36 PM, Ammo Collector wrote:
Hi, we've been receiving lots of Twitter/timeout errors on search
with 502 error codes. The account we use is "klout". I would say 1 in
4 calls to search result in 502s... Any ideas on how to reduce the
errors? Maybe go 50 instead of 100 results?
example call:
http://search.twitter.com/search.atom?q=&from=username&phrase=bit.ly&rpp=100&page=1
