W3C home > Mailing lists > Public > public-webapps@w3.org > July to September 2009

Re: New FileAPI Draft | was Re: FileAPI feedback

From: Gregg Tavares <gman@google.com>
Date: Wed, 5 Aug 2009 01:59:46 -0700
Message-ID: <de4bd3190908050159x214de673r7c1d75028eb3b047@mail.gmail.com>
To: arun@mozilla.com
Cc: Web Applications Working Group WG <public-webapps@w3.org>
On Wed, Aug 5, 2009 at 1:47 AM, Arun Ranganathan <arun@mozilla.com> wrote:

> Gregg Tavares wrote:
>
>> I'd really like to contribute to this as I'm helping implement WebGL and
>> we
>> need a way to get LOTS of data into WebGL. Hundreds of files per app.
>>
>> That said, there's a bunch of things I don't understand about the API
>>
>> *) Given that XMLHttpRequest is limited to a same domain policy
>>
> Firefox 3.5 and Safari 4 support cross-domain XMLHttpRequest, mitigated by
> CORS.  See, for example,
> http://hacks.mozilla.org/2009/07/cross-site-xmlhttprequest-with-cors/
>
>> but the img
>> tag, audio tag, video tag, script tag and others are not, how do you
>> resolve
>> that with the FIle API?
>>
>>
> The File API is meant to talk to your local file system.  It isn't a
> "network download" API, but it seems that's what you want :-).  Perhaps I am
> misunderstanding your question?


Sorry, I was told on the HTML5 list that this is where network downloads and
archive support stuff belonged.

It certain seems like a good fit to me.


>
>
> -- A*
>
Received on Wednesday, 5 August 2009 09:00:25 GMT

This archive was generated by hypermail 2.3.1 : Tuesday, 26 March 2013 18:49:33 GMT