Added request body cache to Request.receive#848
Closed
nikordaris wants to merge 10 commits intoKludex:masterfrom
nikordaris:master
Closed
Added request body cache to Request.receive#848nikordaris wants to merge 10 commits intoKludex:masterfrom nikordaris:master
nikordaris wants to merge 10 commits intoKludex:masterfrom
nikordaris:master
Conversation
Author
|
This is no longer a viable solution with the changes to StreamResponse in v0.13.3. I have an idea of how to cache the body and form in the scope instead of the instance of Request and keep the receive function pure. I'll open a different PR for this solution. |
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.
Adds a request body cache to the receive function that is passed to ASGIApp children. This addresses the root cause of an infinite loop issue described in #847 but does not address the infinite loop itself. There is still a potential need to set a timeout around calling the receive() inside of stream()