- From: Device APIs and Policy Working Group Issue Tracker <sysbot+tracker@w3.org>
- Date: Thu, 12 Nov 2009 08:02:01 +0000 (GMT)
- To: public-device-apis@w3.org
ISSUE-44 (apiHanging): What do APIs hang off of? [APIs — General] http://www.w3.org/2009/dap/track/issues/44 Raised by: Robin Berjon On product: APIs — General one issue we have with APIs is also how they are exposed. Say for instance that the Contacts API has a basic interface providing access to the rest of the functionality called "Contacts". We could: 1) Make it available as a constructor: 2) Make it available as an object already instantiated in the global scope 3) Make a way of requesting that an API be "loaded" 4) Use an object to provide access to all the device APIs 5) Hang it off from a markup element 6) Hang it off from an event object Discussion thread starting at: http://lists.w3.org/Archives/Public/public-device-apis/2009Oct/0008.html which lead to the following observations: • window.navigator has been used many times for this type of APIs • a possible window.navigator.device host for the DAP APIs, with the start of a spec at http://dev.w3.org/2009/dap/device/Overview.html • the need to look at on an API-per-API basis, taking into account the security model, the activation model (e.g. from an event, a markup element), the locking model wrt Web workers • the need to watch for clashes in existing Web content (the latter two points having been raised by Hixie http://lists.w3.org/Archives/Public/public-device-apis/2009Oct/0122.html)
Received on Thursday, 12 November 2009 08:02:09 UTC