- From: Dave Raggett <dsr@w3.org>
- Date: Wed, 16 Nov 2011 09:05:53 +0000
- To: Paul Kinlan <paulkinlan@google.com>
- CC: Charles Pritchard <chuck@jumis.com>, James Hawkins <jhawkins@google.com>, Greg Billock <gbillock@google.com>, Rich Tibbett <richt@opera.com>, Dominique Hazael-Massieux <dom@w3.org>, Robin Berjon <robin@berjon.com>, public-webapps Group WG <public-webapps@w3.org>, "public-device-apis@w3.org public-device-apis@w3.org" <public-device-apis@w3.org>
On 15/11/11 20:46, Paul Kinlan wrote: > This is the way that I have implemented it in test apps. It is the > handler app that will show the progress information. I have not had a > case yet where the client app needs or is concerned about the progress > of the action that is being handled, other than on completion or on error. So you are assuming the handler app always has a client-side API independent of the client app, even if the handler app is itself remote? I am looking forward to the seeing the use cases, as background for the assumptions. > > I will launch a whole lot of new demo's soon so that we can all see them. Looking forward to them. -- Dave Raggett<dsr@w3.org> http://www.w3.org/People/Raggett
Received on Wednesday, 16 November 2011 09:06:34 UTC