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

Re: File API Feedback

From: Michael Nordman <michaeln@google.com>
Date: Wed, 22 Jul 2009 11:26:38 -0700
Message-ID: <fa2eab050907221126m4e55e4c4q4843c0a6cd61230c@mail.gmail.com>
To: Anne van Kesteren <annevk@opera.com>
Cc: arun@mozilla.com, public-webapps@w3.org
On Wed, Jul 22, 2009 at 4:44 AM, Anne van Kesteren <annevk@opera.com> wrote:

> On Wed, 22 Jul 2009 04:07:18 +0200, Arun Ranganathan <arun@mozilla.com>
> wrote:
> > This still sends strings, but XHR 2[2] has got:
> >
> >   void send(in ByteArray data);
> >
> > which makes me think we need a binary getter as well :)
> Yes, it is called responseBody at the moment. I intent to replace both with
> support for FileData (the new Blob as I understand it) whenever that is
> defined and published.

Another aspect of the use case we're discussing (composing a
multipart/form-data POST for sending vis XHR2) is NOT having to actually
read the full contents of the file parts into memory while doing this
composition. That wouldn't work for a large file or for a large number of
smaller files.

Gears BlobBuilder accomplishes that by constructing a resulting Blob that
internally keeps track of a collection of constituent Blobs (some of which
may be memory resident and other backed by a files on disk). When Gears
HttpRequest sends one of these Blobs, it reads things incrementally. So no
big memory usage spikes when dealing with file backed Blobs during
composition of the multipart Blob or during the sending of it (also no big
disk usage spikes during composition or sending).

> > [2] http://www.w3.org/TR/XMLHttpRequest2/#xmlhttprequest
> --
> Anne van Kesteren
> http://annevankesteren.nl/
Received on Thursday, 23 July 2009 05:51:00 UTC

This archive was generated by hypermail 2.3.1 : Friday, 27 October 2017 07:26:17 UTC