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

Re: XHR.responseBlob and BlobWriter [nee FileWriter]

From: Jonas Sicking <jonas@sicking.cc>
Date: Mon, 16 Aug 2010 20:35:20 -0700
Message-ID: <AANLkTik=z99Jr-oLwoWeT=ibcVfAP4sW+6X6viqoKxxV@mail.gmail.com>
To: Michael Nordman <michaeln@google.com>
Cc: Web Applications Working Group WG <public-webapps@w3.org>, Anne van Kesteren <annevk@opera.com>, Eric Uhrhane <ericu@google.com>, Darin Fisher <darin@chromium.org>, James Robinson <jamesr@google.com>, Thomas Broyer <t.broyer@gmail.com>
On Mon, Aug 16, 2010 at 7:05 PM, Michael Nordman <michaeln@google.com> wrote:
> Hi All,
> I'm interested in adding support for XHR.responseBlob to webkit and chrome.
> It sounds like we have a general consensus to add two new members to the
> XmlHttpRequest interface:
>   attribute boolean asBlob;  // at least for the sake of discussion, calling
> it that for now
>   readonly attribute Blob responseBlob;
> Another name option could be 'downloadAsBlob'. Personally, I like 'asBlob'
> for its brevity and its naming similarity to  'withCredentials'.
> Looks like the semantics of when its valid to call setRequestHeaders also
> applies setting the asBlob attribute; after open() but before send() has
> been called. An attempt to set the value at some inappropriate time should
> throw an INVALID_STATE exception. Also the asBlob attribute value should
> probably be reset to 'false' upon return from open(), again similar to how
> the request headers are cleared out upon return from open().
> Anne, have you been following this discussion, wdyt?
> Michael

Sounds good, though I think we let asBlob act is more like
withCredentials and not get reset upon open(). Thus it can also be
settable before open() as well.

/ Jonas
Received on Tuesday, 17 August 2010 03:36:15 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 18:13:10 UTC