W3C home > Mailing lists > Public > public-device-apis@w3.org > January 2010

Re: Why aren't most devices virtual web services?

From: Ilkka Oksanen <Ilkka.Oksanen@nokia.com>
Date: Thu, 14 Jan 2010 11:56:56 +0200
Message-ID: <4B4EEA68.1000202@nokia.com>
To: ext Robin Berjon <robin@robineko.com>
CC: "Mark S. Miller" <erights@google.com>, "public-device-apis@w3.org" <public-device-apis@w3.org>
Robin Berjon wrote:
> Beyond that, a (secondary) worry is the maturity of paraphernalia
> such as JSON Schema and JSONpath that we could want to use here. But
> that's a bridge we can cross any number of ways.

Date objects in parameters or return values can be especially tricky to 
serialize in virtual web server approach. I'm not sure if for example 
JSON has yet proper support for Dates. Dates will be part of the API at 
least in Calendar.

In general I'm bit worried how much overhead XHR processing can cause to 
developers. Assuming I write a simple script that needs Device APIs just 
to read system's temperature. Are the options to either write a parser 
myself to remove the transport encoding or to rely on some convenience 
library that does the decoding? Both options potentially increase script 
size considerably.

Received on Thursday, 14 January 2010 09:58:03 UTC

This archive was generated by hypermail 2.3.1 : Monday, 23 October 2017 14:53:41 UTC