From mboxrd@z Thu Jan  1 00:00:00 1970
X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on polar.synack.me
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00,FREEMAIL_FROM
	autolearn=unavailable autolearn_force=no version=3.4.4
X-Received: by 10.50.203.69 with SMTP id ko5mr9817428igc.2.1460638901214;
        Thu, 14 Apr 2016 06:01:41 -0700 (PDT)
X-Received: by 10.157.35.195 with SMTP id t61mr169913otb.16.1460638901187;
 Thu, 14 Apr 2016 06:01:41 -0700 (PDT)
Path: 
 eternal-september.org!reader01.eternal-september.org!reader02.eternal-september.org!news.eternal-september.org!mx02.eternal-september.org!feeder.eternal-september.org!news.glorb.com!g8no795310igr.0!news-out.google.com!j7ni226igm.0!nntp.google.com!g8no795308igr.0!postnews.google.com!glegroupsg2000goo.googlegroups.com!not-for-mail
Newsgroups: comp.lang.ada
Date: Thu, 14 Apr 2016 06:01:40 -0700 (PDT)
In-Reply-To: <nenq6h$18jn$1@gioia.aioe.org>
Complaints-To: groups-abuse@google.com
Injection-Info: glegroupsg2000goo.googlegroups.com;
 posting-host=193.251.73.50;
 posting-account=O3LyFwoAAACc1uh60ZcOUmAGdDmGsEcV
NNTP-Posting-Host: 193.251.73.50
References: <nejfta$lmg$1@gioia.aioe.org>
 <d536dcf9-e710-4ff7-9953-4272dda304f6@googlegroups.com>
 <nenq6h$18jn$1@gioia.aioe.org>
User-Agent: G2/1.0
MIME-Version: 1.0
Message-ID: <6d3b7ac5-8fc6-406c-8aac-947d25a78249@googlegroups.com>
Subject: Re: Simple Components 4.12 with MQTT implementation released
From: slos <new.stephane.los@gmail.com>
Injection-Date: Thu, 14 Apr 2016 13:01:41 +0000
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Xref: news.eternal-september.org comp.lang.ada:30105
Date: 2016-04-14T06:01:40-07:00
List-Id: <comp.lang.ada>

Le jeudi 14 avril 2016 12:08:23 UTC+2, Dmitry A. Kazakov a =E9crit=A0:
> On 14/04/2016 10:54, slos wrote:
>=20
> > I'm really impressed by and grateful for the hard work.
>=20
> Thanks, though MQTT protocol is not not that hard. The broker, possibly,=
=20
> mainly because I tried to reduce inefficiencies and faults of the MQTT=20
> protocol design as much as possible.
>=20
> I was astonished that MQTT looks quite popular among large, serious SW=20
> houses. Though not surprisingly, considering its faults, there is no any=
=20
> devices supporting MQTT. Without devices, what all these people are=20
> doing with MQTT is a mystery to me... (:-))
>=20
> > I think the provided MQTT features are likely to be very useful for
> > IoT applications and so a must have for the future of Ada.
>=20
> I built it in MAX! home automation application (it controls ELV radiator=
=20
> thermostats), let's see.
>=20
> Bug reports and features requests are welcome.
>=20
> --=20
> Regards,
> Dmitry A. Kazakov
> http://www.dmitry-kazakov.de

I thank you not only for the MQTT implementation but for Simple Components,=
 used among others by Gnoga which I like much too, and also for AIWCL which=
 I would like to see available on Gnoga too.

When looking for MQTT capable devices you could find those at Hilscher for =
example:
http://www.hilscher.com/en/applications/industrial-internet/
http://www.hilscher.com/products/product-groups/industrial-internet-industr=
y-40/

With those announced gateways to the IIOT, many things can be MQTT enabled.

Anyway, every thing is getting "smarter" and MQTT is not the only protocol =
in the arena.

Anyone for OPC ? ;-)
http://open62541.org/

I think Ada could have a bright future in cloud based applications, from th=
e embedded world to the cloud.
Well, it has been designed exactly for this.

And I regard your contribution and the one of David Botton as "qui tombe =
=E0 pic" or "=E0 point nomm=E9", which come in handy or timely.

Sometimes it seems that things just happen like a self arranging puzzle.
It's in the air.

Best Regards,
St=E9phane
http://slo-ist.fr/ada4autom