[webkit-dev] XHR responseArrayBuffer attribute
mjs at apple.com
Mon Sep 27 18:37:54 PDT 2010
On Sep 27, 2010, at 3:19 PM, Michael Nordman wrote:
> Webkit's XHR currently does not keep two copies of the data that I can see. I think we should avoid that.
We could keep the raw data around, which hopefully is directly usable as an ArrayBuffer backing store, and only translate it to text format when/if the client requests responseText.
> On Mon, Sep 27, 2010 at 2:40 PM, Anne van Kesteren <annevankesteren at gmail.com> wrote:
> (I'm subscribed to webkit-dev with a different address.)
> On Mon, Sep 27, 2010 at 8:31 PM, Michael Nordman <michaeln at google.com> wrote:
> > Yes, if we go with telling xhr up front for the array buffer case, I guess
> > an enum would be slightly better.
> I do not think this should be told up front. You already need to keep
> the octet buffer in memory for overrideMimeType to work the way it
> does. We designed responseBlob as an optimization so you would not
> have to deal with the other types. I do not think you can optimize the
> reverse with the design as it stands today.
> In any event, any discussion on changes to the specification really
> ought to happen on public-webapps at w3.org.
> Anne van Kesteren
> webkit-dev mailing list
> webkit-dev at lists.webkit.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the webkit-dev