It may require a slightly different build ecosystem, but looking at Eclipse IoT http://iot.eclipse.org/community.html#projects you may see there are at least 4-5 clients for the same MQTT protocol in languages like Java, JavaScript/Node.js (Ponte), C or Lua, maybe a few more, so we might add a few more options for a DeviceMap client, too.
It seems merely a skeleton, but someone at least thought of that on top of OpenDDR already;-) https://github.com/LTheobald/openddr-api Werner On Wed, Jan 7, 2015 at 7:03 PM, Reza Naghibi <[email protected] > wrote: > Yes, you are exactly right. A Javascript client. It would work exactly > like all the other clients, the algorithm would be exactly the same. We > would just favor it using a more optimized pattern domain to allow for > faster download and lighter processing. Im thinking a few KB max. > > From: Bertrand Delacretaz <[email protected]> > To: [email protected] > Sent: Wednesday, January 7, 2015 12:57 PM > Subject: Re: [DISCUSS] Data 2.0 and a frontend Javascript client > > Hi Reza, > > > > On Wed, Jan 7, 2015 at 6:43 PM, Reza Naghibi > <[email protected]> wrote: > > ...One in particular is a frontend Javascript client... > > Just to make sure I understand correctly, do you mean a piece of > Javascript software that runs in a browser, downloads the current > DeviceMap device data set and uses that to classify the browser based > on its User-Agent? > > If yes, I'd rather call this a "javascript client" as that could also > run server-side in environments like Node.js besides the very > interesting client-only setup that you suggest. > > -Bertrand > > > >
