Confirmed users
69
edits
FirefoxOS/Device Storage: Difference between revisions
Added some pro
(Created page with "= Device Storage = == Active Contributors == Dev: Dave Hylands and Andrew Osmond QA: No-jun Park == Documentation == == Bug Backlog == == Projects == === New Architectu...") |
(Added some pro) |
||
| Line 23: | Line 23: | ||
<bugzilla> | <bugzilla> | ||
{ | { | ||
"product":" | "product":"Core", | ||
"target_milestone":"", | "target_milestone":"", | ||
"whiteboard":"NG Device Storage", | "whiteboard":"NG Device Storage", | ||
| Line 30: | Line 30: | ||
} | } | ||
</bugzilla> | </bugzilla> | ||
=== Device Storage Service Workers === | |||
Update the current Device Storage API implementation so that it can be used by Service Workers. | |||
=== Device Storage Database === | |||
Currently, device storage doesn't persist any information from the storage areas, and each app that uses device storage needs to create its own database with all of the meta data associated with the various files. | |||
Having Device Storage maintain a database would mean that the apps wouldn't need to scan media each time that they run. Device Storage knows when media is inserted an removed, so it has a much better idea of when the media needs to be rescanned. Also, by persisting the information in a database, it would allow device storage to return ordered enumerations. Currently the files are returned in filesystem order, and all files need to be enumerated in order to get a sorted list. | |||
=== MTP Automation and Testing === | |||
Currently, much of the MTP testing is manual. We need to come up with methods and tests to allow a significant portion of this to be automated. Especially since particular clients (i.e. Windows) expect particular types of responses, so weneed to ensure that we continue to deliver those responses | |||