These are chat archives for esp8266/Arduino

14th
Aug 2018
Rushikesh Patel
@luffykesh
Aug 14 2018 16:14
I have opened a new issue #5044 @earlephilhower @devyte
Develo
@devyte
Aug 14 2018 17:24
I see it, thank you
hillct
@hillct
Aug 14 2018 18:22
It appears my issue above relates to ESPHTTPUpdate’s dependency upon ESPHTTPClient, and lack of flexibility in that regard. It would be helpful if one could pass an alternate HttpClient object to ESPHTTPUpdate, for example the ESPASyncHTTPClient, such that ESPHTTPUpdate would then be compatible with the Async http stack
Earle F. Philhower, III
@earlephilhower
Aug 14 2018 19:27
@hillct PR's always appreciated! However, unless the ESPAsyncHTTPClient is a subclass of ESPHTTPClient and implements the same interface (and the methods are all virtual (sorry @devyte)) it feels like it will be a big PR.
hillct
@hillct
Aug 14 2018 20:09
@earlephilhower @devyte well, here’s hoping that it’s a proper subclass. @me-no-dev mentioned it’s existance but I haven’t yet been able to locate it. Worst case, I’d be reimplementing using related AsyncTCP classes, but either way, I guess I’ll be brushing off the 30 year old Kernighan and ritchie… fun fun
Develo
@devyte
Aug 14 2018 20:32
virtualness is like a cross between a plague and a tar pit
hillct
@hillct
Aug 14 2018 22:07
that’s confidence inspiring… I thought someone would at least remind me that K&R barely touches on modern C++
Earle F. Philhower, III
@earlephilhower
Aug 14 2018 22:48

Actually, I'd hazard a guess that K & R doesn't touch on any C++ whatsoever. You'll be wanting Stroustrup instead. Don't worry about @devyte, virtual is not a dirty word. :)

That said, AsyncTCP is not a child of WiFiClient (or any other class) and has a completely different API because it is callback based. So, while not impossible, it looks like a massive undertaking on your part.

den har
@denman0000_gitlab
Aug 14 2018 23:29
Hi guys .. ..just curious .. is there a way to just send 32bits (4 bytes) through from one esp to another and still have ack/nack ? I tried the UDP example which is fine but not the most reliable and doesnt seem to catch all packets escepially if the receiver is idle for a while so then tried the TCP webserver example (not that i need a server at all ) ... i would like to have one master and multiple clients/slaves ... the payload increased to 45 bytes
any suggestions or help/advice would be very welcome.
hillct
@hillct
Aug 14 2018 23:38
@earlephilhower actually, AsyncTCP had a SyncClient class which is meant specifically to reproduce the interface of the WifiClient class, for cases exactly like this (supposedly). That said, it’s still an undertaking, well beyond my very old, out of date C-fu