this is a 'good
thing to do' but not 'a critical thing to do', its odds 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 A
t;
> On Tue, Nov 5, 2013 at 12:19 PM, Anne van Kesteren wrote:
>
>> On Thu, Oct 31, 2013 at 2:12 AM, Brian Stell wrote:
>> > There could be *dozens* of copies of exactly the same a Javascript
>> library,
>> > shared CSS, or web font in the FileSystem.
>>
-hotmail-yahoo-email-users/
>
> 2013/10/31 Brian Stell :
> > In "Request for feedback: Filesystem API" [1] it says "This filesystem
> would
> > be origin-specific".
> >
> > This post discusses limited readonly sharing of filesystem resourc
s its files
(readonly) by persistent URL
I'm not asking-for nor suggesting API file access but others may express
opinions on this.
Brian Stell
PS: Did I somehow miss info on same-origin in the spec [7]?
Notes:
[1]
http://lists.w3.org/Archives/Public/public-script-coord/2013JulSep/0379.html
[
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.
>>>
>>
>>
I meant
eg, V1/dir1/file1, V2/dir1/file1.
/dir1/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
