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

Re: Devices as Virtual Web Services

From: Max Froumentin <maxfro@opera.com>
Date: Wed, 20 Jan 2010 18:03:03 +0100
Message-ID: <4B573747.60902@opera.com>
To: Robin Berjon <robin@robineko.com>
CC: public-device-apis@w3.org
On 20/01/2010 15:32, Robin Berjon wrote:
> Hi all,
>
> as discussed previously, here are my notes about this specific issue:
>
>    http://dev.w3.org/2009/dap/docs/virtual-ws.html
>
> Comments welcome!

DAP as an API means:
- It is implemented in the browser code, or a plugin
- It is simple to use for webapp authors (because it was designed so)

DAP as a REST service means:
- more work for webapp authors (and there are thousands more of them 
than browser implementers.)
- hence, webapp authors will almost be forced to use a framework
- that framework will probably need to include Comet support
- we're not sure yet if every feature of DAP is mappable to a REST concept.
- we're not sure how to solve the URI scheme problem.

Based on the above, and on the assumption that DAP is meant to be a 
convenience for webapp authors, APIs seem simpler and superior.

But like John Kemp has said, it's a good thing to keep REST 
implementations in mind when we design the API, since we can expect a 
few of them to be wrappers around REST APIs anyway.

Whether we should have a REST solution defined on top of the current API 
is something we may want to have a look at, but not a priority to me.

Max.
Received on Wednesday, 20 January 2010 17:03:42 GMT

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