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

Re: [whatwg] Fetch: number of tasks queued

From: Anne van Kesteren <annevk@annevk.nl>
Date: Wed, 13 Mar 2013 15:14:05 +0000
Message-ID: <CADnb78iDYHj-Q4DF_VtsnG1q3du2Wf8p-=iW-O=2hjPzJ85Ayg@mail.gmail.com>
To: Boris Zbarsky <bzbarsky@mit.edu>
Cc: whatwg@lists.whatwg.org
On Wed, Mar 13, 2013 at 2:52 PM, Boris Zbarsky <bzbarsky@mit.edu> wrote:
> 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.

However, if all data is typically available during state 3, developers
might rely on that. Not queuing a special task that triggers state 3
for data: URLs does not preclude asynchronous loading at all.

Received on Wednesday, 13 March 2013 15:14:34 UTC

This archive was generated by hypermail 2.4.0 : Wednesday, 22 January 2020 16:59:56 UTC