PhysicHTTP folder to ESPAsyncWebServer

[ewowi]

No description provided.

[thedemoncat]

Hi!
A much-anticipated improvement! When can I try it out?

[ewowi]

Nobody has sufficient time at the moment to do it, so no date set yet. But if you want to help, let's talk !

[thedemoncat]

I will try to remove the time next week and see how difficult it will be.

It would be a good idea to accept this MR in a separate branch so that we can work together to achieve success. Or should I suggest the MR to your fork?

Another question is, have you already considered the benefits of replacing the web server? What exactly will be better, and what is the main reason for the replacement?

[theelims]

Well, actually the project started with ESPAsnycWebserver. But I replaced it in Release v0.3.0 due to the unstable performance at that time.

Benefits with ESPAsyncWebserver:

• less heap consumption
• more concurrent (# of clients) connections to the server

[ewowi]

It would be a good idea to accept this MR in a separate branch so that we can work together to achieve success. Or should I suggest the MR to your fork?

I have this PR also in my fork of this repo and asked CodeRabbit to make a plan , see ewowi#1

I recently have Claude Code, I think Claude code can do it for 99%

So check the plan there, and let me know what you think

[thedemoncat]

@theelims I did the migration. Everything seemed to go well. MR created in the fork of @ewowi

[ewowi]

@theelims I did the migration. Everything seemed to go well. MR created in the fork of @ewowi

That's amazing! Thanks a lot, will try soon.

Not using less heap is a pity. But I still think this is the right choice. Any other changes in behavior? Speed? Flash size ?

[thedemoncat]

@ewowi I moved MR directly to the main repository