Quart -> aiohttp #25
Merged
Quart -> aiohttp #25
Conversation
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
Owner
Author
|
Has been able to handle ~45k request/24 hour, should be fine to merge - One less dependency, woop!
|
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.
Goal of this is to deprecate Quart in favour of having one less dependency while also running a more native web server that aiohttp has to offer. It also makes more sense to run with the library that is already being used for both WebSocket and outgoing HTTP requests. This is already ready for release, however I won't merge it until it has been tested fully. Currently it runs on a bot that has 8M viewable users with around 40 interactions/minute.