W3C home > Mailing lists > Public > public-device-apis@w3.org > March 2012

RE: [sensor] Feedback to Geolocation WG on Device Orientation?

From: SULLIVAN, BRYAN L <bs3131@att.com>
Date: Fri, 16 Mar 2012 02:53:06 +0000
To: Marcos Caceres <w3c@marcosc.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>
Message-ID: <59A39E87EA9F964A836299497B686C350F47DCE5@WABOTH9MSGUSR8A.ITServices.sbc.com>
Agreed, even the sensor may be accessed over a network connection of any type... the controls we are talking about affect only the behavior of the first hop (the webapp API implementation) in delivering the events. How that affects what happens under the hood can leverage/affect any number of functions in a particular implementation.

Bryan Sullivan

-----Original Message-----
From: Marcos Caceres [mailto:w3c@marcosc.com] 
Sent: Thursday, March 15, 2012 3:33 PM
Cc: Tran, Dzung D; Frederick.Hirsch@nokia.com; public-device-apis@w3.org
Subject: Re: [sensor] Feedback to Geolocation WG on Device Orientation?

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

Received on Friday, 16 March 2012 02:54:11 UTC

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