[Feature request] lwIP and mbedTLS port

[caerbannog]

[Feature request] lwIP and mbedTLS port

[Caerbannog]

I suppose that newcomers to the embedded world, and people stumbling on posts explaining esphttpclient will be grateful if the interface does not change that much, and no toolchain settings need to be altered.

But I think that you are probably more qualified than me to make the decision, as I didn't manage to configure lwip the last time I tried. Your arguments seem to be good, so here are the options:

• Publish a v2 release, explain in the README the differences with v1. Maybe explain how to get v1 if you're a newbie.
• Or fork the lib, maybe rename it, and edit the base README to recommend moving to the fork.

[flannelhead]

I totally agree with your comment.

Hence, I think forking and renaming is the optimal way to handle this. The fork could be presented as an alternative or a "similar project" as that's what it shall be. Your library is perfectly fine and usable as-is: it supports SSL and can be linked against the official Espressif SDK without any patches.

The fork would be linked against lwip_open which is supplied by esp-open-sdk. Also, forking gives the freedom to not have feature parity (e.g. not have response buffering in the library, not have SSL/TLS in the beginning).

Does this sound OK to you?

[Caerbannog]

Yes :)

[flannelhead]

Sadly, I have not had time to work on the matter discussed here, and don't have a need for the planned fork any longer - hence closing this issue.