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:49:13 +0100
To: 'Ian Hickson' <ian@hixie.ch>, Frederick Hirsch <frederick.hirsch@nokia.com>
CC: "public-device-apis@w3.org" <public-device-apis@w3.org>
Message-ID: <6DFA1B20D858A14488A66D6EEDF26AA3232A1FB277@seldmbx03.corpusers.net>
You might be right. Ideally a REST approach seems more attractive. However, I express a humble view as with REST there might be issues around need for additional protocols, URIs, security etc. 

Claes

> -----Original Message-----
> From: public-device-apis-request@w3.org [mailto:public-device-apis-
> request@w3.org] On Behalf Of Ian Hickson
> Sent: onsdag den 10 februari 2010 13:12
> To: Frederick Hirsch
> Cc: public-device-apis@w3.org
> Subject: Re: Devices as Virtual Web Services
> 
> On Wed, 10 Feb 2010, Frederick Hirsch wrote:
> >
> > Is the executive summary here:
> >
> > 1. Standardize Javascript APIs for all device functionality in the
> DAP
> > charter
> >
> > 2. Expose REST interface to those APIs where appropriate, using those
> > APIs to implement
> 
> Isn't the whole point of #2 to make #1 unnecessary?
> 
> --
> Ian Hickson               U+1047E                )\._.,--....,'``.
> fL
> http://ln.hixie.ch/       U+263A                /,   _.. \   _\  ;`._ ,.
> Things that are impossible just take longer.   `._.-(,_..'--(,_..'`-
> .;.'
Received on Wednesday, 10 February 2010 12:49:46 UTC

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