David is correct.
There certainly are use cases for having Webapps share data. Not just data
in filesystem's, but also structured data stored in something like
localStorage or IndexedDB.
However this filesystem API proposal does not address those use cases.
If someone would like to come up with a proposal for data sharing between
Webapps they should feel free to do so. Such a proposal would need to also
include a description of a security model.
But again, the current proposal does not address that use case.
/ Jonas
On Oct 22, 2014 3:30 AM, "David Rajchenbach-Teller" <dteller@mozilla.com>
wrote:
> I don't see a contradiction.
> Each *web* app sees only files accessible from its domain (so your two
> apps have distinct "pic.jpeg").
> Each *native* app has access to whatever the operating system says.
>
> Or am I missing something in your message?
>
> Cheers,
> David
>
> On 22/10/14 12:23, Jonathan Bond-Caron wrote:
> > That contradicts:
> > - Edited files should be accessible by other client-side applications
> >
> > The api should allow for editing a 'shared folder' which multiple
> applications / web apps can access.
> > That implies a sort of locking/unlocking api:
> >
> > e.g.
> > photo editor
> > fs = api.getFileSystem({shareName: "photos"}).then((dir) => {
> dir.openWrite("pic.jpeg") });
> >
> > super photo viewer
> > fs = api.getFileSystem({shareName: "photos"}).then((dir) => {
> dir.openRead("pic.jpeg") });
> >
> > What happens with the pic.jpeg?
> >
> >
>
>
> --
> David Rajchenbach-Teller, PhD
> Performance Team, Mozilla
>
>
Received on Wednesday, 22 October 2014 15:29:37 UTC