mirror of
https://github.com/tzapu/WiFiManager.git
synced 2026-04-27 09:05:56 +03:00
[GH-ISSUE #158] Support Async TCP and Async Webserver #122
Labels
No labels
📶 WiFi
🕸️ HTTP
Branch
DEV Help Wanted
Discussion
Documentation
ESP32
Example
Good First Issue
Hotfix
In Progress
Incomplete
Needs Feeback
Priority
QA
Question
Task
Upstream/Dependancy
bug
duplicate
enhancement
invalid
pull-request
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/WiFiManager#122
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @kaeferfreund on GitHub (Apr 24, 2016).
Original GitHub issue: https://github.com/tzapu/WiFiManager/issues/158
Hi,
since I have switched to async tcp and web server by me-no-dev, things have gotten a lot faster. But sadly the WiFi Manager doesn't work anymore, bec its based on the "normal" WebServer Library.
Would appreciate if we could port the WiFi Manager to async
@alanswx commented on GitHub (Jul 2, 2016):
Here is a first version of this - it needs some work still:
https://github.com/alanswx/ESPAsyncWiFiManager
Also it should have a non-modal mode.
@btomer commented on GitHub (Nov 6, 2016):
If anyone is still interested in this, I wrote a WiFiManager fork that supports ESPAsyncWebServer and behaves exactly the same as the current version of WiFiManager (from master):
https://github.com/btomer/WiFiManager
@kentaylor commented on GitHub (Nov 8, 2016):
I'm interested, partly because I don't like rebooting after WiFi manager completes . A WiFiManager that blocks until completion is a good design for some scenarios and I understand it will not with the ESPAsyncWebServer, is that correct? I see that you have a compiler directive to choose which web server version to use. Why was that design decision made rather than only having the ESPAsyncWebServer? Would you be willing to add your changes to this version of WiFiManager? It is quite a bit different from the Tzapu version now and while I can figure out what you've done and copy, you would be able do it more easily.
@tzapu commented on GitHub (Nov 8, 2016):
@kaeferfreund adding async web server to wifimanager, while there s no async webserver in the core would mean people would need to add another library, which would raise the entry barrier.
The way that @btomer did it though, could certainly sort that.
nice work @btomer , thanks. i m sure people will find it usefull. maybe i should compile all these links/branches in a list
@kentaylor i wrote a POC some time ago that lets you use a webserver with WiFiManager without reseting. I m sure it can be adapted to your sketches, see here https://gist.github.com/tzapu/ecc0759829d30d5a6152
@rjsachse commented on GitHub (Jun 7, 2018):
Would be good to implement @btomer way with a simple define
@dronecz commented on GitHub (Jul 24, 2020):
@tablatronix Is there any chance that async web server will be included in WiFiManager? I´m trying to change actual code to work with define as @btomer did, but so far no luck. Thx
@tablatronix commented on GitHub (Jul 24, 2020):
It should be easy to do in development alpha.m version
@nferch commented on GitHub (Dec 30, 2020):
rebased and updated @btomer 's patch against master branch a while back at https://github.com/nferch/WiFiManager/tree/asyncwebserver
@tablatronix commented on GitHub (Dec 30, 2020):
FYI this is in async branch based off development, do not maintain forks
#1121