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

RE: Device Storage API

From: SULLIVAN, BRYAN L <bs3131@att.com>
Date: Fri, 1 Jun 2012 19:27:37 +0000
To: Steve VanDeBogart <vandebo@google.com>
CC: Doug Turner <dougt@mozilla.com>, Frederick Hirsch <Frederick.Hirsch@nokia.com>, "public-device-apis@w3.org" <public-device-apis@w3.org>
Message-ID: <59A39E87EA9F964A836299497B686C350FEE8CBB@WABOTH9MSGUSR8D.ITServices.sbc.com>
Comment inline.

Bryan Sullivan

From: Steve VanDeBogart [mailto:vandebo@google.com]
Sent: Friday, June 01, 2012 12:01 PM
Cc: Doug Turner; Frederick Hirsch; public-device-apis@w3.org
Subject: Re: Device Storage API

I certainly can understand the appeal of separating different media types into different virtual containers, especially in the mobile context where file storage is generally abstracted away from the user. However, in the desktop environment I think it will end up confusing the users. If the user stores their pictures and videos from a particular event in a folder then when viewed through this kind of API those items get pulled apart into two different hierarchies. I prefer to preserve the user's organization system to minimize the user's confusion.

<bryan> I believe in most cases the app would choose the storage abstraction that makes sense for the media type, and if there are options, perhaps present them to the user e.g. the option to store visual media in "pictures" or "videos". The other options are to defer all storage decisions to the UA (e.g. based upon media type: too limiting) or to the user (e.g. based upon their explicit choice or selection of specific filesystem locations: too intrusive, difficult, and inconsistent in constrained devices). There is a balance in letting the app use abstractions and still offer the user the ability as appropriate to select the preferred abstraction.

On Fri, Jun 1, 2012 at 5:59 AM, SULLIVAN, BRYAN L <bs3131@att.com<mailto:bs3131@att.com>> wrote:
Using well-known and user-familiar abstractions such as "pictures", "music", "video", "documents", "temp", etc is a good approach. We used that in the concept of file system "roots" in the WAC FileSystem API, and it's an easy thing for developers to leverage to point right to where they want to store/access files. It's also useful in presenting options to users for those data storage functions.

Bryan Sullivan

-----Original Message-----
From: Doug Turner [mailto:dougt@mozilla.com<mailto:dougt@mozilla.com>]
Sent: Wednesday, May 30, 2012 8:38 AM
To: Frederick Hirsch
Cc: public-device-apis@w3.org<mailto:public-device-apis@w3.org>
Subject: Re: Device Storage API

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<mailto:Frederick.Hirsch@nokia.com>>
To: public-device-apis@w3.org<mailto:public-device-apis@w3.org>
Cc: "Frederick Hirsch" <Frederick.Hirsch@nokia.com<mailto: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 Friday, 1 June 2012 19:28:56 UTC

This archive was generated by hypermail 2.3.1 : Monday, 23 October 2017 14:53:54 UTC