RE: flush() | was Re: FileSystem API Comments

2014-11-06 Thread Ali Alabbas
nt: Friday, October 31, 2014 11:19 AM To: Ali Alabbas Cc: Web Applications Working Group WG Subject: flush() | was Re: FileSystem API Comments Greetings Ali! I've been thinking about the discussion of flush(), and would like to see if I can make my previous statement a bit more nuanced. It turns

flush() | was Re: FileSystem API Comments

2014-10-31 Thread Arun Ranganathan
Greetings Ali! I’ve been thinking about the discussion of flush(), and would like to see if I can make my previous statement a bit more nuanced. It turns out that flush() (in the vein of fsync/sync) is pretty useful, and after discussion with a few folks within Mozilla, I realize that it isn’t

Re: FileSystem API Comments

2014-10-22 Thread Arun Ranganathan
Ali, First, thanks for your timely comments :) I’m in the process of editing the FileSystem API. Responses inline: On Oct 21, 2014, at 4:36 PM, Ali Alabbas wrote: > > 1.1 Use cases (3. Audio/Photo editor with offline access or local cache for > speed) > > * Edited files should be acces

Re: FileSystem API Comments

2014-10-22 Thread Jonas Sicking
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

Re: FileSystem API Comments

2014-10-22 Thread chaals
22.10.2014, 12:32, "David Rajchenbach-Teller" : > 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. There are a lot of use cases for sharing

Re: FileSystem API Comments

2014-10-22 Thread David Rajchenbach-Teller
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

RE: FileSystem API Comments

2014-10-22 Thread Jonathan Bond-Caron
On Tue Oct 21 09:36 PM, Jonas Sicking wrote: > > 1.1 Use cases (3. Audio/Photo editor with offline access or local > > cache for > > speed) > > > > * Edited files should be accessible by other client-side > > applications > > > > - Having the sandboxed file system share its contents between

Re: FileSystem API Comments

2014-10-21 Thread Jonas Sicking
On Tue, Oct 21, 2014 at 1:36 PM, Ali Alabbas wrote: > Hello, > > I'm with the IE Platform team at Microsoft. We have a few comments on the > latest editor's draft of the newly proposed FileSystem API [1]. Hi Ali! Thanks for looking at the spec. I'm glad you've been able to understand the API as w

Re: FileSystem API Comments

2014-10-21 Thread Arthur Barstow
On 10/21/14 4:36 PM, Ali Alabbas wrote: Hello, I'm with the IE Platform team at Microsoft. We have a few comments on the latest editor's draft of the newly proposed FileSystem API [1]. I believe [1] is Arun's . 1.1 Use cases (3. Audio/Ph

FileSystem API Comments

2014-10-21 Thread Ali Alabbas
Hello, I'm with the IE Platform team at Microsoft. We have a few comments on the latest editor's draft of the newly proposed FileSystem API [1]. 1.1 Use cases (3. Audio/Photo editor with offline access or local cache for speed) * Edited files should be accessible by other client-side applica