Re: Polished FileSystem API proposal

2013-11-06 Thread Brian Stell
of getting implemented are poor. Brian Stell Notes: [1] https://github.com/slightlyoff/ServiceWorker [2] https://github.com/slightlyoff/ServiceWorker/blob/master/caching.md On Wed, Nov 6, 2013 at 8:28 AM, pira...@gmail.com pira...@gmail.com wrote: That's very interesting and useful, but I

Re: Polished FileSystem API proposal

2013-11-05 Thread Brian Stell
-hotmail-yahoo-email-users/ 2013/10/31 Brian Stell bst...@google.com: In Request for feedback: Filesystem API [1] it says This filesystem would be origin-specific. This post discusses limited readonly sharing of filesystem resources between origins. To improve web site

Re: Polished FileSystem API proposal

2013-11-05 Thread Brian Stell
ann...@annevk.nlwrote: On Thu, Oct 31, 2013 at 2:12 AM, Brian Stell bst...@google.com wrote: There could be *dozens* of copies of exactly the same a Javascript library, shared CSS, or web font in the FileSystem. Check out the cache part of https://github.com/slightlyoff/ServiceWorker

Re: Polished FileSystem API proposal

2013-10-30 Thread Brian Stell
are peculiar to Unix filesystems. Not interoperable across all OSes. Symbolic links, OTOH... /be Brian Stell mailto:bst...@google.com October 29, 2013 4:53 PM I meant eg, V1/dir1/file1, V2/dir1/file1.

Re: Polished FileSystem API proposal

2013-10-29 Thread Brian Stell
I meant eg, V1/dir1/file1, V2/dir1/file1.

Re: Polished FileSystem API proposal

2013-10-28 Thread Brian Stell
/file1. It would possible to copy the unchanged files but that would double the storage size. Could you kindly share your thoughts on having a link API? Thanks, Brian Stell Notes: [1] http://linux.die.net/man/2/link