feat: Add rate limiting functionality to API requests#34
Open
IOITI wants to merge 1 commit intohootnot:masterfrom
Open
feat: Add rate limiting functionality to API requests#34IOITI wants to merge 1 commit intohootnot:masterfrom
IOITI wants to merge 1 commit intohootnot:masterfrom
Conversation
Owner
|
Hi, |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Hi !
Thanks for your API Handler ! I'm using it in my project WATA !
This PR adds a
RateLimiterclass to properly handle Saxo Bank's API rate limits. The implementation respects both the session rate limits reported in response headers and implements a smart waiting mechanism to avoid hitting rate limits.Changes:
RateLimiterclass that tracks remaining request quota and reset timesBenefits:
Implementation details:
This should help users of your library, in order to avoid hitting rate limits when making multiple API calls in quick succession, especially in automated trading scenarios :)