ESPAsyncTCP
ESPAsyncTCP copied to clipboard
me-no-dev
Async TCP Library for ESP8266
I have copied AsyncPrinter to AsyncTCP for ESP32, and it has thrown an exception on connect. It looks like the check for a valid buffer pointer is negated: https://github.com/me-no-dev/ESPAsyncTCP/blob/15476867dcbab906c0f1d47a7f63cdde223abeab/src/AsyncPrinter.cpp#L107...L110 And...
Used methods `write` or `add` no possible send to client more than 1072 bytes. Method `AsyncClient::send()` no clean buffer.
Hi, I want to send a string to my client. I don't want to send it as answer, just when connection established the esp8266 try to send a string to...
Let's say, for example: without of this flag it's can't start asyncwebserver on 80 port after wifimanager(also on 80) is shutdowned. But wifimanager still may be started, because in "WiFiServer.cpp"...
I installed the zip version for my esp8266 as it is not part of official arduino ibraries? It installs in arduino libraries folder AsyncTCP-master/ in the src folder the files...
Corrected missed edit for _recv() in ASYNC_TCP_SSL_ENABLED in AsyncServer::_poll(). And other missed edit for `errorTracker` around ASYNC_TCP_SSL_ENABLED. This should resolve @kasedy comment https://github.com/me-no-dev/ESPAsyncTCP/pull/115#issuecomment-538816623 and @mcspr. Tested ASYNC_TCP_SSL_ENABLED using marvinroger/async-mqtt-client/ ......
Rebased https://github.com/me-no-dev/ESPAsyncTCP/pull/129 as requested by https://github.com/kleini @me-no-dev Please apply this pull request so building of SSL with ESPAsyncTCP works again.
Fixes onAck not firing after ungraceful disconnect with unacked data left. See issue https://github.com/me-no-dev/ESPAsyncTCP/issues/160
In my project sometimes it fails to handle response. I propose not to check client connected on RX No side effects revealed
