Re: [aerogear-dev] AeroGear Messaging

Envoyé de mon iPhone Le 22 avr. 2015 à 17:36, Summers Pittman <supittma(a)redhat.com&gt; a écrit : On Wed, Apr 22, 2015 at 2:01 AM, Erik Jan de Wit <edewit(a)redhat.com&gt; wrote: > So when I think IoT, I would think one of the challenges would be that > you have a lot of things. So what would be useful would be a way to > discover these devices on the network maybe? > What type of network? I know with TCP/IP there are some utilities for finding things on your local subnet. There are also things wifi direct does but I am not familiar with them. What type of protocol do the iBeacon family of devices use over BLE? I think beacons use Bluetooth and thus it's discovery facilities I suppose that explains the B in BLE ;)

> On Tue, Apr 21, 2015 at 10:03 PM, Burr Sutter <bsutter(a)redhat.com&gt; wrote: > > > > On Apr 21, 2015, at 10:50 AM, Summers Pittman <supittma(a)redhat.com&gt; > wrote: > > > > > > > > On Tue, Apr 21, 2015 at 10:43 AM, Burr Sutter <bsutter(a)redhat.com&gt; > wrote: > >> > >> We already have ActiveMQ, a message broker that will deal with things > like > >> “durable subscriptions”, holding messages until the subscriber wakes > up and > >> acknowledges receipt. > >> > >> There is also Mosca as a Node.js-based MQTT focused message broker. > >> > >> There will be a wide spectrum of Things - from most distributed edge > >> sensors with energy harvesting (smart dust) to robust “gateway” > servers > >> that look a lot like your typical datacenter server today. It is > currently > >> unclear to me which of the application protocols will “win”. At this > >> moment, MQTT is a winner (great support from numerous vendors) and I > feel > >> that CoAP will be a winner as well. > >> AMQP or DDS may win on the beefier gateways but not so much edge > >> intelligent things. > > > > > > MQTT seems to work pretty OK on Android (last I checked). > > > > What type of messaging APIs would be useful on mobile hosts? I > > > > > > I am not sure…lots of folks here to provide some insights :-) > > > > > > > > Does an IOT webapp even make sense? (There is probably something to be > said > > for ChromeOS apps) > > > > If the Thing is beefy enough to run a web browser then I consider it to > be a > > mobile use case, less an IoT use case scenario. > > > > > > > >> > >> > >> > >> On Apr 21, 2015, at 10:22 AM, Summers Pittman <supittma(a)redhat.com&gt; > wrote: > >> > >> > >> > >> On Tue, Apr 21, 2015 at 10:19 AM, Matthias Wessendorf < > matzew(a)apache.org&gt; > >> wrote: > >>> > >>> more something like a unified messanger platform, where we have real > >>> messaging hooks/adapters (client/server) for protocols like AMQP, > MQTT, XMPP > >>> etc while having support for push notifications as well. > >> > >> We could probably extend the Push API. I mean it already does half the > >> work for us ;) > >>> > >>> > >>> That would be nice to have, at some point > >>> > >>> On Tue, Apr 21, 2015 at 4:13 PM, Luke Holmquist <lholmqui(a)redhat.com&gt; > >>> wrote: > >>>> > >>>> like Notifier? > >>>> > >>>> On Tue, Apr 21, 2015 at 10:02 AM, Summers Pittman < > supittma(a)redhat.com&gt; > >>>> wrote: > >>>>> > >>>>> So IoT is getting a lot of attention within the company (or at least > >>>>> within my monkeysphere). From the demo project I've noticed that a > lot of > >>>>> the work is in messaging and message handling. What do you guys > think about > >>>>> exploring this space more? How does it / can it /should it fit > into our > >>>>> roadmap? > >>>>> > >>>>> > >>>>> > >>>>> _______________________________________________ > >>>>> aerogear-dev mailing list > >>>>> aerogear-dev(a)lists.jboss.org > >>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev > >>>> > >>>> > >>>> > >>>> _______________________________________________ > >>>> aerogear-dev mailing list > >>>> aerogear-dev(a)lists.jboss.org > >>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev > >>> > >>> > >>> > >>> > >>> -- > >>> Matthias Wessendorf > >>> > >>> blog: http://matthiaswessendorf.wordpress.com/ > >>> sessions: http://www.slideshare.net/mwessendorf > >>> twitter: http://twitter.com/mwessendorf > >>> > >>> _______________________________________________ > >>> aerogear-dev mailing list > >>> aerogear-dev(a)lists.jboss.org > >>> https://lists.jboss.org/mailman/listinfo/aerogear-dev > >> > >> > >> _______________________________________________ > >> aerogear-dev mailing list > >> aerogear-dev(a)lists.jboss.org > >> https://lists.jboss.org/mailman/listinfo/aerogear-dev > >> > >> > >> > >> _______________________________________________ > >> aerogear-dev mailing list > >> aerogear-dev(a)lists.jboss.org > >> https://lists.jboss.org/mailman/listinfo/aerogear-dev > > > > > > _______________________________________________ > > aerogear-dev mailing list > > aerogear-dev(a)lists.jboss.org > > https://lists.jboss.org/mailman/listinfo/aerogear-dev > > > > > > > > _______________________________________________ > > aerogear-dev mailing list > > aerogear-dev(a)lists.jboss.org > > https://lists.jboss.org/mailman/listinfo/aerogear-dev > > > > -- > Cheers, > Erik Jan > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev(a)lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev > _______________________________________________ aerogear-dev mailing list aerogear-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/aerogear-dev _______________________________________________ aerogear-dev mailing list aerogear-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/aerogear-dev