Re: Introduction of WebI2C and WebGPIO

I think I understand this, but I don’t understand where WoT fits in. 

As far as I can tell, it’s about embedded programming. The CHIRMEN board doesn’t seem to have a network connection or a display connection.

It’s an embedded linux computer with GPIOs that runs a browser environment as an embedded programming environment. A developer writes html with embedded javascript and local GPIO and I2C javascript libraries in order to program hardware sensors and actuators which are directly connected to the board’s I/O pins.

So basically a developer can pretend they're programming in a browser using HTML and javascript and tags and stuff when programming an embedded linux based controller. I guess you write the code using your favorite web design tool and then download it to the board, where it executes and blinks the LED.

Am I missing something important?

Cheers,

Michael


On Oct 14, 2015, at 12:05 PM, Drasko DRASKOVIC <drasko.draskovic@gmail.com> wrote:

> On Wed, Oct 14, 2015 at 9:00 PM, Dave Raggett <dsr@w3.org> wrote:
>> 
>> On 14 Oct 2015, at 19:20, Drasko DRASKOVIC <drasko.draskovic@gmail.com>
>> wrote:
>> 
>> 
>> While CoAP has a browser support only in Firefox currently (via
>> Copper), MQTT support is even easier - for example via lib like this
>> https://github.com/mqttjs/MQTT.js which can send MQTT messages via
>> WebSocket.
>> 
>> 
>> Does this rely on a server side Web Sockets to MQTT gateway of some kind?
> 
> Modern MQTT brokers contain WS support for this purpose - example:
> http://jpmens.net/2014/07/03/the-mosquitto-mqtt-broker-gets-websockets-support/
> and https://github.com/mcollina/mosca/wiki/MQTT-over-Websockets.
> 
> BR,
> Drasko
> 

Received on Thursday, 15 October 2015 01:34:02 UTC