- From: Marcos Caceres <w3c@marcosc.com>
- Date: Thu, 15 Mar 2012 22:33:23 +0000
- To: SULLIVAN, BRYAN L <bs3131@att.com>
- Cc: Tran, Dzung D <dzung.d.tran@intel.com>, "Frederick.Hirsch@nokia.com" <Frederick.Hirsch@nokia.com>, "public-device-apis@w3.org" <public-device-apis@w3.org>
On Thursday, 15 March 2012 at 16:39, SULLIVAN, BRYAN L wrote: > Thanks Dzung, that captures my general understanding. Having written signaling software dealing with low-level signal sensor integration, I can relate to the value of both handing that function off to a OS-level API while give the app the ability to set the criteria that makes sense for it. There are multiple layers in between the sensor and the application. We should make no assumption that the there is a direct link between the web application, it's timing model, the OS, it's timing model, and the timing model of the sensor (which could be controlled by both hardware and software). Each will have it's own timing and could be controlled independently by separate parts of the software and hardware (i.e., completely separate from the Web app, which could (and will likely) just be talking to a proxy of the sensor and not the sensor itself). -- Marcos Caceres http://datadriven.com.au
Received on Thursday, 15 March 2012 22:33:59 UTC