Library: Replace ESPAsyncWebServer library #780
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
|
When spamming the board with the traditional F5-torture test, the Wifi function has significantly lower execution time |
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.
What
This PR replaces the me-no-dev/ESPAsyncWebServer library in favour of the more supported mathieucarbou/ESPAsyncWebServer
At the same time we replace the me-no-dev/AsyncTCP library, with the mathieucarbou/AsyncTCPsock instead.
Why
See the list of improvements in the changes in this fork section for why we should switch ESPAsyncWebserver. There are also performance gains by switching AsyncTCP over to AsyncTCPsock
How
Direct replacement of ESPAsyncWebServer library. Webserver feels faster now 🚈