[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [lwip-users] Tunnel solution for HTTP server expose to Internet
From: |
Sergio R. Caprile |
Subject: |
Re: [lwip-users] Tunnel solution for HTTP server expose to Internet |
Date: |
Mon, 9 Apr 2018 10:00:40 -0300 |
User-agent: |
Mozilla/5.0 (Windows NT 6.1; rv:52.0) Gecko/20100101 Thunderbird/52.7.0 |
My personal opinion follows:
Do you absolutely need HTTP ?
As long as we don't have IPv6 (and fixed addresses), we have to go DDNS
and port forwarding. Yes, this requires an end user holding a PhD or at
least the techie ones. So... the whole purpose of "the cloud" probably
started with this, and so many developers resort to publishing on some
publisher/subscriber architecture and either provide a web frontend
based on a subscriber backend or a subscriber based smartphone
application (or computer program). Enter MQTT, available in your lwIP repo.
Do you absolutely need HTTP ?
An ellaborated explanation is a bit off-topic (and extense).
You can do this with a hosted server and database for one or a few
devices. You should also consider Heroku. For lots of devices, a cloud
service like Amazon AWS, Google Cloud, that bunch of money makers based
on Seattle, or even Adafruit is probably a better idea.
For remote control, however, the MQTT way is a bit more involved, so for
a verbose interface you would probably want to run a more friendly
protocol on top of that.
Everything depends on what you need to do and how you want to interact
with your devices.