Re: XHR responseArrayBuffer attribute: suggestion to replace "asBlob" with "responseType" from Darin Fisher on 2010-10-27 (public-webapps@w3.org from October to December 2010)

From: Darin Fisher <darin@chromium.org>
Date: Wed, 27 Oct 2010 00:21:11 -0700
To: Boris Zbarsky <bzbarsky@mit.edu>
Cc: Anne van Kesteren <annevk@opera.com>, Chris Rogers <crogers@google.com>, Web Applications Working Group WG <public-webapps@w3.org>, Eric Uhrhane <ericu@google.com>, michaeln@google.com, Alexey Proskuryakov <ap@webkit.org>, Chris Marrin <cmarrin@apple.com>, Geoffrey Garen <ggaren@apple.com>, jorlow@google.com
Message-ID: <AANLkTi=jKD9UpPu7LKQK+DGx65heP4V_B0xjCKDzLq4g@mail.gmail.com>

On Wed, Oct 27, 2010 at 12:04 AM, Boris Zbarsky <bzbarsky@mit.edu> wrote:

> On 10/27/10 2:28 AM, Darin Fisher wrote:
>
>> I think it's about performance as well as implementor convenience.  If
>> the implementor knows up front that the data should be stored as a Blob,
>> then the implementor can write the data to disk without having to waste
>> memory.
>>
>
> I have no problem with hinting to the implementor that the result is
> expected to be used as a Blob so they can optimistically store it to disk.
>  My problem is with then making it impossible to get it as a string if
> needed later (which would just involve reading the data from disk into
> memory).
>
> -Boris
>


Yes, but doing so is inefficient since the API requires the data to be in
memory synchronously.  We don't want to block the UI thread on disk IO.

-Darin

Received on Wednesday, 27 October 2010 07:21:52 UTC