Re: [File System APIs] If one is good, then two must be better?

Hi,

> In which case, what Cordova does (and more to the point what developers do with it) seems relevant information to consider as we try to find a consensus.

For what it’s worth, we’re currently building a mobile app for use with both Cordova and Web browsers.

The main use case of our app is caching large video files and playing them back directly from the filesystem. So filesystem URLs are a critical feature there.

Other than that, the callback-based approach of the Google proposal let us end up in callback hell right from the start, so we wrapped the whole API in promises as best as we could, just to make it usable for our app developers. In that department, Mozilla’s promises-based proposal might be much cleaner and easier to work with.

Cheers,
Basti

On 4 Feb 2014, at 15:15, Charles McCathie Nevile <chaals@yandex-team.ru> wrote:

> On Mon, 03 Feb 2014 19:09:53 +0400, Arthur Barstow <art.barstow@nokia.com> wrote:
> 
>> On 1/31/14 10:44 AM, ext Ian Clelland wrote:
>>> Hi Art,
>>> 
>>> For what it's worth, theFile API: Directories and System is also implemented (and supported) by Apache Cordova[1]. The implementation is essentially complete for mobile applications on Android, iOS and FireOS, with nearly-complete support on Blackberry and Windows Phone.
>>> 
>>> While our plugin registry was counting downloads, it was the most-downloaded plugin for the platform by a wide margin, so I believe it is being used actively.
>> 
>> Thanks for this information Ian!
>> 
>>> I don't know if Cordova should count as a browser implementation for the purposes of this WG, but we are implementing the APIs and making them available to (hybrid) web application developers.
>> 
>> The group has some flexibility regarding the specifics of the interoperability criteria used to advance a spec along the Recommendation track, but we haven't talked about the criteria for these specs since they are still working drafts.
> 
> And the particular question here isn't about CR criteria, but about whether one or other approach is more likely to achieve the consensus of interoperable implementation.
> 
> Which essentially means whether implementations are likely to switch, or credible future implementors have a strong preference for one over the other.
> 
> In which case, what Cordova does (and more to the point what developers do with it) seems relevant information to consider as we try to find a consensus.
> 
> cheers
> 
> Chaals
> 
> -- 
> Charles McCathie Nevile - Consultant (web standards) CTO Office, Yandex
>      chaals@yandex-team.ru         Find more at http://yandex.com