cordova-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From rodms10 <>
Subject [GitHub] cordova-plugin-file pull request: [FxOS] Support for resolve URI, ...
Date Mon, 21 Jul 2014 22:38:31 GMT
GitHub user rodms10 opened a pull request:

    [FxOS] Support for resolve URI, request all paths and local app directory.

    Updated file plugin in preparation for file-transfer plugin implementation. Main change
is support for `resolveLocalFileSystemURL` which is needed for file-transfer. I'm also better
isolating the filesystems. We now support 3 data paths:
     * `applicationDirectory` - Uses `xhr` to get local files that are packaged with the app.
     * `dataDirectory` - For persistent app-specific data files.
     * `cacheDirectory` - Cached files that should survive app restarts (Apps should not rely
on the OS to delete files in here).
    ### Technical info
    To figure out which filesystem to use, file plugin calls the `__format__` function defined
in `www/firefoxos/FileSystem.js`, where you have a chance to alter the path sent to the plugin.
Over there we add the filesystem name to the full path. Later, the function `resolveToFullPath_`
will get a modified full path and return the storage path to be used in indexeddb, the full
path of the entry and the file name.
    @zalun, can you take a look?

You can merge this pull request into a Git repository by running:

    $ git pull resolveurl

Alternatively you can review and apply these changes as the patch at:

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #64
commit b33b6fdb581249d1fae94ad585135a5d33ee38df
Author: Rodrigo Silveira <>
Date:   2014-07-09T22:46:50Z

    Support for resolve URI, request all paths and local app directory.


If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at or file a JIRA ticket
with INFRA.

View raw message