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

Re: Device Storage API

From: Doug Turner <dougt@mozilla.com>
Date: Wed, 30 May 2012 08:38:01 -0700 (PDT)
To: Frederick Hirsch <Frederick.Hirsch@nokia.com>
Cc: public-device-apis@w3.org
Message-ID: <592612237.1969053.1338392281052.JavaMail.root@mozilla.com>
right, the Device Storage API leaves it up to the implementation to define what "file systems" are backing the storage.  I say that because you could have an implementation that uses a database instead of a file system directory.  The main entry point of the API allows you to pass what storage you're interested.  Our implementation for basically maps "pictures" to where on the file system pictures exists. 

----- Original Message -----
From: "Frederick Hirsch" <Frederick.Hirsch@nokia.com>
To: public-device-apis@w3.org
Cc: "Frederick Hirsch" <Frederick.Hirsch@nokia.com>
Sent: Wednesday, May 30, 2012 7:00:47 AM
Subject: Re: Device Storage API


I think it is worth discussing this Device Storage API in DAP, thanks for mentioning it.

It is in the scope of gallery, which in the charter is for  "Gallery API, an API to manage the local media file storage" (sounds similar to the Device Storage API description you gave)  http://www.w3.org/2011/07/DeviceAPICharter

Is one difference of the Device Storage API and File System API that the device storage API might be limited to a more restricted portion of the file system than the file API? (e.g. limited to a media area?)
Could this be a difference (responding to the question on the wiki page)


regards, Frederick

Frederick Hirsch
Received on Wednesday, 30 May 2012 15:38:30 UTC

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