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

RE: Devices as Virtual Web Services

From: Nilsson, Claes1 <Claes1.Nilsson@sonyericsson.com>
Date: Wed, 10 Feb 2010 13:58:18 +0100
To: 'Anne van Kesteren' <annevk@opera.com>, Frederick Hirsch <Frederick.Hirsch@nokia.com>, ext Ian Hickson <ian@hixie.ch>
CC: "public-device-apis@w3.org" <public-device-apis@w3.org>
Message-ID: <6DFA1B20D858A14488A66D6EEDF26AA3232A1FB27A@seldmbx03.corpusers.net>
Wouldn't that be covered by "your favorite JS library/framework" ?



> -----Original Message-----
> From: Anne van Kesteren [mailto:annevk@opera.com]
> Sent: onsdag den 10 februari 2010 13:56
> To: Nilsson, Claes1; Frederick Hirsch; ext Ian Hickson
> Cc: public-device-apis@w3.org
> Subject: Re: Devices as Virtual Web Services
> 
> On Wed, 10 Feb 2010 13:52:40 +0100, Nilsson, Claes1
> <Claes1.Nilsson@sonyericsson.com> wrote:
> > Yes, there are different implementation alternatives. However, with a
> > REST approach it is possible to implement "device APIs" through a
> local
> > (downloadable) server. This opens up for API extensibility.
> 
> Maybe. I think you still need some amount of browser involvement to let
> the user associate services with the URI the API evolves around and
> indicate which other services may access the data.
> 
> 
> --
> Anne van Kesteren
> http://annevankesteren.nl/

Received on Wednesday, 10 February 2010 12:58:51 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 19:32:17 UTC