Thiago:
>> If you're going to communicate with a tiny MCU connected over a mesh
>> network like 6LoWPAN/Thread, you won't be using TCP. Much less HTTP.

and you'll want that MCU running something light-weight in C++, not a
web-bloat thing.  So Qt is just the thing for the job.

(... and I had to google MCU - microcontroller unit, not Marvel Comic Universe 
;^)

Jean-Michaël Celerier (29 August 2017 10:20)
> What makes me a bit sad is that if Qt's not doing it, then we end up
> having to put up with bloated stuff like Node.JS on beagleboard or
> raspberries :
> https://www.postscapes.com/javascript-and-the-internet-of-things/
> which are now more and more used.  Hell, sometimes people use python
> of all languages on constrained CPUs.  It's a niche that Qt *could*
> fill, and fill better than the alternatives.

We are aware of it [*] and looking at what to do.
We are, however, short of hands and up to our necks in things to do.

[*] https://wiki.qt.io/Qt_Network_Workshop_2016#IoT

        Eddy.
_______________________________________________
Development mailing list
[email protected]
http://lists.qt-project.org/mailman/listinfo/development

Reply via email to