You probably want to pay the most attention to the "X-RateLimit-Remaining" header, which is the number of requests you can make before being rate-limited. It's a good practice to monitor this value and throttle your requests if necessary.
The X-RateLimit-Reset timestamp indicates when you'll recover the maximum number of Hits (X-RateLimit-Limit) for the class (X-RateLimit-Class) your request falls into.
-- Arnaud / @rno
On Fri, Apr 1, 2011 at 11:31 AM, Tom Mc <uggnot@gmail.com> wrote:
I've been looking at the ratelimiting response headers and have found
some documentation, but nothing that provides me with sample values
and what they mean.
I'm developing an application in ColdFusion and using scribe (in java)
for the OAuth library.
I'm getting the headers back fine (at least X-RateLimit-Reset, I
haven't hit the ratelimit for Search to see what it looks like yet)
and I can read them in. That isn't the problem. What I'm having
difficulty with is what the number that actually comes back.
It appears to be a specific time in Seconds since 1/1/1970, but when I
do the calculations, regardless of if i've hit the rate-limit I always
get a time back that is 1 hour in the future. I feel like I'm just
making a stupid mistake and overlooking something, but any help that
you can provide would be much appreciated.
Thanks,
Tom McConlogue
--
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
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
No comments:
Post a Comment