[webkit-dev] XHR responseArrayBuffer attribute: possible implementation
darin at chromium.org
Mon Oct 25 15:04:48 PDT 2010
How do you address the discoverability issue that I raised? asBlob and
asArrayBuffer have the benefit of being detectable at runtime. but, a
settable responseType does not support detection of supported values.
On Mon, Oct 25, 2010 at 2:54 PM, Chris Rogers <crogers at google.com> wrote:
> passing "undefined" as the 4th and 5th arguments seems pretty clunky to me.
> Since, we already have an "asBlob" attribute, then "asArrayBuffer" like
> Darin suggests seems like it might be better. However, then we can get into
> cases where both "asBlob" and "asArrayBuffer" are set, and this problem
> would get even worse as new types are added. So, an attribute called
> "responseType" might be a good solution. This would be instead of passing
> it as an argument to open(), and instead of having an "asBlob" attribute.
> This approach seems the cleanest to me, and I'll propose it to the
> appropriate standards group.
> On Mon, Oct 25, 2010 at 12:45 PM, Alexey Proskuryakov <ap at webkit.org>wrote:
>> 25.10.2010, в 12:34, Chris Marrin написал(а):
>> request.open("GET", "data.xml", true, "Text");
>>> request.open("GET", "data.xml", true, "XML");
>>> request.open("GET", "data.xml", true, "Bytes");
>> I'd sure like to try to avoid an explosion in the API. I like Geoff's
>> suggestion of specifying the type of request in open(). Seems like the best
>> API would be to have Geoff's API and then:
>> Note that open() has username and password as its 4th and 5th arguments.
>> So, you'd have to call it like request.open("GET", "data.xml", true,
>> undefined, undefined, "Bytes");
>> - WBR, Alexey Proskuryakov
>> webkit-dev mailing list
>> webkit-dev at lists.webkit.org
> webkit-dev mailing list
> webkit-dev at lists.webkit.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the webkit-dev