Re: Polished FileSystem API proposal

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 / application performance I'm interested in caching
static [2] resources (eg, Javascript libraries, common CSS, fonts) in the
filesystem and accessing them thru persistent URLs.

So, what is the issue?

I'd like to avoid duplication. Consider the following sites: they are all
from a single organization but have different specific origins;
   * https://mail.google.com/
   * https://plus.google.com/
   * https://sites.google.com/
   * ...

At google there are *dozens* of these origins [3]. Even within a single
page there are iframes from different origins. (There are other things that
lead to different origins but for this post I'm ignoring them [4].)

There could be *dozens* of copies of exactly the same a Javascript library,
shared CSS, or web font in the FileSystem.

What I'm suggesting is:
   * a filesystem's persistent URLs by default be read/write only for the
same origin
   * the origin be able to allow other origins to access 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
[2] I'm also assuming immutability would be handled similar to gstatic.com [6]
where different versions of a file have a different path/filename; eg,
   * V8: http://gstatic.com/fonts/roboto/v8/2UX7WLTfW3W8TclTUvlFyQ.woff
   * V9: http://gstatic.com/fonts/roboto/v9/2UX7WLTfW3W8TclTUvlFyQ.woff

[3] Here are some of Google's origins:
https://accounts.google.com
https://blogsearch.google.com
https://books.google.com
https://chrome.google.com
https://cloud.google.com
https://code.google.com
https://csi.gstatic.com
https://developers.google.com
https://docs.google.com
https://drive.google.com
https://earth.google.com
https://fonts.googleapis.com
https://groups.google.com
https://mail.google.com
https://maps.google.com
https://news.google.com
https://www.panoramio.com
https://picasa.google.com
https://picasaweb.google.com
https://play.google.com
https://productforums.google.com
https://plus.google.com/
https://research.google.com
https://support.google.com
https://sites.google.com
https://ssl.gstatic.com
https://translate.google.com
https://tables.googlelabs.com
https://talkgadget.google.com
https://themes.googleusercontent.com/
https://www.blogger.com
https://www.google.com
https://www.gstatic.com
https://www.orcut.com
https://www.youtube.com

My guess is that there are more.

I believe the XXX.blogspot.com origins belong to Google but I'm not an
authority on this.

[4] These are also different top level domains:
   * https://www.google.nl
   * https://www.google.co.jp

Wikipedia lists about 200 of these [5] but since users tend to stick to one
I'm ignoring them for this posting.

I'm also ignoring http vs https (eg, http://www.google.com) and
with/without leading www (eg, https://google.com) since they redirect.

[5] http://en.wikipedia.org/wiki/List_of_Google_domains
[6] http://wiki.answers.com/Q/What_is_gstatic
[7] http://w3c.github.io/filesystem-api/Overview.html