- From: Satoru Takagi <sa-takagi@kddi.com>
- Date: Wed, 14 Oct 2015 18:11:53 +0900
- To: futomi.hatano@newphoria.co.jp, drasko.draskovic@gmail.com
- Cc: public-device-apis@w3.org, public-wot-ig@w3.org, public-browserobo@w3.org, tobie@sensors.codespeaks.com
> > I think you should take a look at WeIO (http://we-io.com), > The site seems to be down. Probably it is this. http://we-io.net/ It seems to resemble tessel. https://tessel.io/ We are interested in browser technologies in particular. I seem to be worth researching the relations with them, at a viewpoint of delivering web technologies to maker movement and reconsidering a role of server and client, Satoru Takagi > On Wed, 14 Oct 2015 08:35:32 +0200 > Drasko DRASKOVIC <drasko.draskovic@gmail.com> wrote: > > > Hello Satoru, > > Interesting project. > > > > I think you should take a look at WeIO (http://we-io.com), which has Python > > WS server embedded on the board and exposes JavaSript API (to be used in > > browser) to manipulate the HW. > > The site seems to be down. I could not view the site. > It is not JavaScript API, is it? > > Anyway, the local-server architecture is realistic for now. > But the architecture works only in systems which allow > us to install a websocket server or a web server freely > and easily. > > I don't deny the architecture. It will be usefull forever. > But there are many situations which not allow us to > install any servers freely and easily, such as Firefox OS. > Besides, W3C is not appropriate for standardization of > such architecture. > > The local-server architecture has a disadvantage. > It is latency. > If browsers implement GPIO/I2C API directly, > the disadvantage would be solved. > > We need both of the archtectures. > > Cheers, > Futomi > > -- > Newphoria Corporation > Chief Technology Officer > Futomi Hatano > -- > futomi.hatano@newphoria.co.jp > http://www.newphoria.co.jp/ > > > > > BR, > > Drasko > > On Oct 14, 2015 7:49 AM, "Satoru Takagi" <sa-takagi@kddi.com> wrote: > > > > > Hello, > > > We want to introduce WebI2C *1 and WebGPIO *2 API to you. > > > > > > These APIs are becoming to be implemented on the newly designed board > > > computer that B2G works. [MozOpenHard Project] *3 > > > > > > Anyone may be able to create various sensors by themselves in conformity > > > with Generic Sensor API by using computer having these APIs and easily > > > available I2C devices. > > > > > > In addition, we have a plan to do demonstration and breakout about these at > > > TPAC. > > > > > > *1: WebI2C : https://github.com/browserobo/WebI2C > > > *2: WebGPIO : https://github.com/browserobo/WebGPIO > > > *3: MozOpenHard Project : http://mozopenhard.mozillafactory.org/ > > > > > > Regards, > > > > > > Satoru Takagi > > > > > > > > > >
Received on Wednesday, 14 October 2015 09:12:50 UTC