ethernet stack - httpclient versus wifi and ethernet client
Posted: Thu Aug 12, 2021 2:54 am
Dear community,
I saw recently that the esp8266 library has been enriched with ethernet capability and would be able to use a driver for W5500 chip natively.
However, it looks like this has been added without considering utilities classes such httpclient that use to be independant from a WiFiClient. You could instantiate it without a client but now you have to call the constructor by passing such class
The immediate consequence is that the code that was woring with past version of the board (in my case 2.7.4) and separate library (lww550 driver) is not working anymore with 3.x.x framework.
Ideally, implementation should consider getting a generic Client class and then you would pass either an Ethernet or a WiFi client. I am not sure how and to whom to address this design fix (there are probably others)
Thanks for your support.
I saw recently that the esp8266 library has been enriched with ethernet capability and would be able to use a driver for W5500 chip natively.
However, it looks like this has been added without considering utilities classes such httpclient that use to be independant from a WiFiClient. You could instantiate it without a client but now you have to call the constructor by passing such class
The immediate consequence is that the code that was woring with past version of the board (in my case 2.7.4) and separate library (lww550 driver) is not working anymore with 3.x.x framework.
Ideally, implementation should consider getting a generic Client class and then you would pass either an Ethernet or a WiFi client. I am not sure how and to whom to address this design fix (there are probably others)
Thanks for your support.