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:52:40 +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: <6DFA1B20D858A14488A66D6EEDF26AA3232A1FB278@seldmbx03.corpusers.net>
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.

Claes

> -----Original Message-----
> From: public-device-apis-request@w3.org [mailto:public-device-apis-
> request@w3.org] On Behalf Of Anne van Kesteren
> Sent: onsdag den 10 februari 2010 13:27
> To: Frederick Hirsch; ext Ian Hickson
> Cc: public-device-apis@w3.org
> Subject: Re: Devices as Virtual Web Services
> 
> On Wed, 10 Feb 2010 13:22:14 +0100, Frederick Hirsch
> <Frederick.Hirsch@nokia.com> wrote:
> > I was repeating what I heard in Claes's message.
> >
> > Running a local web server to have local access seems overkill,
> leading
> > to the thought that both  might be necessary. I haven't seen a
> concrete
> > proposal apart from what Robin put together.
> 
> A local Web server is overkill. A browser could just have special
> semantics for certain types of requests initiated through
> XMLHttpRequest.
> And since these REST-based APIs need a special URI to be instantiated
> (e.g. data-service:contacts/...) that should be easy to do.
> 
> 
> --
> Anne van Kesteren
> http://annevankesteren.nl/


Received on Wednesday, 10 February 2010 12:53:15 UTC

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