[docs] x-ratelimit-reset-after #1069
Merged
Conversation
This file contains 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
aquarial
added a commit
to discord-haskell/discord-haskell
that referenced
this pull request
Oct 6, 2019
Why I hardcoded paths: #16 Why it's no longer necessary: discord/discord-api-docs#1069
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.
Following up with #1064 - turns out, syncing clocks is a non-trivial task for some platforms/runtimes. So, if you can't sync your clocks for whatever reason, you can now use
X-RateLimit-Reset-Afterto inform you of when the current bucket resets - with the caveat that network latency will cause you to be less efficient than usingX-RateLimit-Resetwith a synchronized clock source.