Rate limiting is guessing about redd HOT 3 CLOSED

Apologies for the late reply. I was aware of the X-Ratelimit-* headers before I began working on the project. The problem with using the headers is that requests then end up getting sent in huge bursts, leaving no requests for the rest of the interval. With this method, most users will never have to worry about the rate limit class at all and requests get sent in equal intervals, so more data is collected. This is the method PRAW uses.

On the wiki's API page, it looks like they also recommend this approach right before the section about the headers.

Make no more than thirty requests per minute. This allows some burstiness to your requests, but keep it sane. On average, we should see no more than one request every two seconds from you.

They seem to recommend using the headers as a double-check, but as far as I know, reddit doesn't block you for overflowing that once in a while, so a request every two seconds seems fine to me. I'll close the issue, but if you have other reasons to think the other approach is better, I'll be happy to re-open the issue.

from redd.

Since I introduced a RateLimit#burst! method (which doesn't sleep for a certain number of requests), the rate limiting was no longer constant, so I had to figure out a way to still make it work. Then I remembered your issue and implemented the X-Ratelimit headers (see d68d96e). So thanks for your suggestion!

from redd.

Awesome!

On Sun Feb 22 2015 at 12:20:46 AM Avinash Dwarapu [email protected]
wrote:

Since I introduced a RateLimit#burst! method (which doesn't sleep for a
certain number of requests), the rate limiting was no longer constant, so I
had to figure out a way to still make rate limiting work. Then I remembered
your issue and implemented the X-Ratelimit headers (see d68d96e
d68d96e).
So thanks for your suggestion!

—
Reply to this email directly or view it on GitHub
#7 (comment).

from redd.