[EDU-6113] - AI Documentation update - 2025-01-24 - upstash rate limiting integration #1472
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
…not develop custom functions, and users must create their own solutions or submit feature requests for additional functionalities like randomized idle time in rate limiting. This addresses users' questions about the possibility of creating custom rate limiting functions with specific features. A note was added to highlight this limitation. Additionally, guidance on using Upstash with rate limiting was maintained, ensuring clarity on what users can do with the current integration. Código: 19007
…not develop custom functions, and users must create their own solutions or submit feature requests for additional functionalities like randomized idle time in rate limiting. This addresses users' questions about the possibility of creating custom rate limiting functions with specific features. A note was added to highlight this limitation. Additionally, guidance on using Upstash with rate limiting was maintained, ensuring clarity on what users can do with the current integration. Código: 19007
| @@ -24,6 +24,10 @@ With this integration, based on an edge function, you can define: | |||
|
|
|||
| Upstash Rate Limiting is integrated with the `upstash/ratelimit` library and provides a global accounting of the rate limit, summing up all the requests received across the entire network, instead of counting separately for each edge location. | |||
|
|
|||
| :::note | |||
| **Important:** Azion does not develop custom functions. Users must create their own solutions or submit feature requests if they require additional functionalities such as randomized idle time in rate limiting. | |||
There was a problem hiding this comment.
Suggested change
| **Important:** Azion does not develop custom functions. Users must create their own solutions or submit feature requests if they require additional functionalities such as randomized idle time in rate limiting. | |
| Azion doesn't develop custom functions. Users must create their own solutions or submit feature requests if they require additional functionalities such as randomized idle time in rate limiting. |
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.
AI Comment: The documentation was updated to clarify that Azion does not develop custom functions, and users must create their own solutions or submit feature requests for additional functionalities like randomized idle time in rate limiting. This addresses users' questions about the possibility of creating custom rate limiting functions with specific features. A note was added to highlight this limitation. Additionally, guidance on using Upstash with rate limiting was maintained, ensuring clarity on what users can do with the current integration.
Código: 19007