W3C home > Mailing lists > Public > whatwg@whatwg.org > March 2013

Re: [whatwg] Fetch: number of tasks queued

From: Boris Zbarsky <bzbarsky@MIT.EDU>
Date: Wed, 13 Mar 2013 10:52:48 -0400
Message-ID: <514092C0.7000900@mit.edu>
To: whatwg@lists.whatwg.org
On 3/13/13 10:36 AM, Anne van Kesteren wrote:
> For the "data:text/html," case Gecko reports both 2 and 4. For
> "data:text/html,test" you get 2, 3 test, 4 test. Chrome/Safari
> dispatch 4 (without test) and then throw mentioning a synchronous
> request. Seems very much like an implementation bug. IE10 throws on
> the open() call which is a bug too. I'm leaning towards just reporting
> 4 for data/about as all the data is already in.

Why do you think it's in?

In gecko all fetch activity is always asynchronous, independent of URL 
scheme.  Furthermore, the network layer can chunk up the "data 
available" callbacks however it wants to ease implementation.  Nothing 
requires it to keep data: in a single flat buffer.

I'm strongly opposed to creating scheme-based special cases here based 
on assumptions about implementation techniques.

-Boris
Received on Wednesday, 13 March 2013 14:53:19 GMT

This archive was generated by hypermail 2.3.1 : Wednesday, 13 March 2013 14:53:19 GMT