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

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

From: John Kemp <john@jkemp.net>
Date: Thu, 14 Jan 2010 15:25:13 -0500
Cc: Robin Berjon <robin@robineko.com>, Ilkka Oksanen <Ilkka.Oksanen@nokia.com>, "Mark S. Miller" <erights@google.com>, "public-device-apis@w3.org Policy WG" <public-device-apis@w3.org>, Kenton Varda <kenton@google.com>
Message-Id: <909C4070-B56F-4F8A-B78D-5A21C9A68194@jkemp.net>
To: Ian Hickson <ian@hixie.ch>
On Jan 14, 2010, at 3:00 PM, Ian Hickson wrote:

> On Thu, 14 Jan 2010, John Kemp wrote:
>> 
>> We are designing Javascript APIs here. Those APIs involve making 
>> Javascript calls.
> 
> Is this a requirement? If so, why? It seems like if it makes more sense to 
> expose something as a RESTful API exposed with a custom scheme handled 
> natively by the UA, then we should do that, rather than expose things as a 
> JavaScript API.

I think what likely makes most sense is what Kenton suggested earlier - a WebIDL binding for RESTful services. That way we should get equivalence between the JS API and the RESTful model without having to specify entirely separate ways (or a new way) of doing things. 

Regards,

- johnk
Received on Thursday, 14 January 2010 20:25:47 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Wednesday, 9 May 2012 00:14:05 GMT