Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Handle Rate Limiting #5

Open
runpaint opened this issue Apr 20, 2009 · 0 comments
Open

Handle Rate Limiting #5

runpaint opened this issue Apr 20, 2009 · 0 comments
Labels
Good to have

Comments

@runpaint
Copy link
Contributor

The API documentation hints that users are limited to a maximum of sixty requests per minute. We need to detect when we are being limited, and if necessary perform exponential backoff until the window has elapsed.

Hopefully we’ll be able to detect rate limiting by looking at the status code, but if not we may need to use an internal counter.
francois2metz added a commit to francois2metz/octopi that referenced this issue Oct 20, 2011
@francois2metz
Handle the rate limiting fcoury#5.
80757ef 
* cache the last value of x-ratelimit-remaining header
* sleep 1 minute if the cache is equals to 0

Signed-off-by: François de Metz <francois@2metz.fr>
@francois2metz francois2metz mentioned this issue Oct 21, 2011
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
Good to have
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Proposal to handle rate limiting francois2metz/octopi
1 participant
@runpaint