Il 09/04/2018 15:00, Sergio R. Caprile ha scritto:
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,
Yes, I agree with you.

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 ?
No, I don't need absolutely HTTP, but HTTP allows the end user to use a standard Web browser (and allow me to avoid writing an app for Android, iOS, ...).

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.
First of all, many of these services aren't free. And I admit my ignorance around those topics. For example, is it possible to avoid writing an app for smartphone? I don't know.

Moreover, are the status of all my devices stored somewhere in the cloud? In this case, I should think of privacy, security, attacks from hackers... it's another job.

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.

Thank you for your suggestions... I'll study a little more on MQTT and related scenarios

_______________________________________________
lwip-users mailing list
lwip-users@nongnu.org
https://lists.nongnu.org/mailman/listinfo/lwip-users

Reply via email to