Re: [twitter-dev] Rate limit HTTP responses

2011-03-21 Thread hax0rsteve
No one ? On 20 Mar 2011, at 17:43, hax0rsteve wrote: Hi all, A question w/r/t HTTP responses when rate limiting is applied, which I'm hoping some kind soul will answer before I start hammering away at the API in careless experimentation : 420 Enhance Your Calm I understand

Re: [twitter-dev] Rate limit HTTP responses

2011-03-21 Thread Taylor Singletary
Hi there Steve, As you've noticed, Search API rate limiting is applied and handled quite differently from the rest of the REST API. In the case of Search, when everything is operating under typical conditions, a Retry-After HTTP header will be sent to you (not an X-Retry-Header) -- the value of

Re: [twitter-dev] Rate limit HTTP responses

2011-03-21 Thread hax0rsteve
Thanks Taylor, that's the info I need :) hax0rsteve On 21 Mar 2011, at 18:57, Taylor Singletary wrote: Hi there Steve, As you've noticed, Search API rate limiting is applied and handled quite differently from the rest of the REST API. In the case of Search, when everything is

[twitter-dev] Rate limit HTTP responses

2011-03-20 Thread hax0rsteve
Hi all, A question w/r/t HTTP responses when rate limiting is applied, which I'm hoping some kind soul will answer before I start hammering away at the API in careless experimentation : 420 Enhance Your Calm I understand from the docs that when this status code is returned, a Retry-After