Replies: 7 comments 12 replies
-
Hi @Pablo2048, are you using same code for both platforms in your project? |
Beta Was this translation helpful? Give feedback.
-
Hi @Pablo2048 : Infos in the release notes ;-) https://github.com/mathieucarbou/ESPAsyncWebServer/releases Don't forget that as per the semver convention each major digit increase is a breaking change, and you can control dependency lookup with for example FYI there is a pending PR that is pending review from @vortigont before I merge it that will put back the _P methods but with a deprecation notice to help ease the pain for people ;-) |
Beta Was this translation helpful? Give feedback.
-
Moving to discussion as this is not an issue report. |
Beta Was this translation helpful? Give feedback.
-
So far I've changed things like this: #if defined(ESP32)
request->send(200, "application/json", "{}");
#else
request->send_P(200, PSTR("application/json"), PSTR("{}"));
#endif and #if defined(ESP32)
request->beginResponse(200, TEXTHTML, index_htm, index_htm_len);
#else
request->send_P(200, TEXTHTML, index_htm, index_htm_len);
#endif |
Beta Was this translation helpful? Give feedback.
-
@mathieucarbou any chance you might be interested in this? - Community Platformio support for Arduino core 3.0.3 |
Beta Was this translation helpful? Give feedback.
-
Hi @mathieucarbou @vortigont - as a huge user of ESPAsyncWS I've been following this project closely - I haven't yet made the switch over to this fork (I'll need to do a PR for msgPack support first). I was wondering, with the recent refactoring have you done any memory profiling? Firmware size is not a real issue for me as my projects all run on ESP32-S3 with 16MB + extra PSRAM. But available heap memory and the max alloc buffer is an important factor, which is why I didn't go with PsychicHTTP. |
Beta Was this translation helpful? Give feedback.
-
Had not done any profiling, but actually it's all pretty straight forward. Mem is allocated only for tcp socket buffers and on messages enqueue. So as long it does not leak it all depends on Q size and number of clients connected. |
Beta Was this translation helpful? Give feedback.
-
Hi guys,
thanks for the hard work. This is no an issue, but info about what need to be done if one want to use latest 3.0.2 version in ESP8266 and ESP32 mixed environment.
const
(ieAsyncWebParameter * p = request->getParam(i);
is nowconst AsyncWebParameter * p = request->getParam(i);
_P
methods for ESP32 are missing ie.request->send_P(...
is nowrequest->send(...
but only for ESP32. For ESP8266 you have to still use_P(...
beginResponse
ierequest->send_P(200, TEXTHTML, index_htm, index_htm_len);
is nowrequest->beginResponse(200, TEXTHTML, index_htm, index_htm_len);
but again only for the ESP32.That is all I found out so far. Now I'm testing long term stability...
Beta Was this translation helpful? Give feedback.
All reactions