Direct Messages usually aren't cached, so they return these errors a lot
more often. If you get a 502, just keep trying until you get a proper
response. (Limit the amount of requests to 10, of course)

Tom


On 11/8/10 9:23 PM, Aaron Rankin wrote:
> Is this expected due to capacity or other infrastructure problems? Or,
> am I doing something wrong?
> 
> 
> Thanks,
> Aaron
> 

-- 
Twitter developer documentation and resources: http://dev.twitter.com/doc
API updates via Twitter: http://twitter.com/twitterapi
Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list
Change your membership to this group: 
http://groups.google.com/group/twitter-development-talk

Reply via email to