[whatwg] Fetch: number of tasks queued
Anne van Kesteren
annevk at annevk.nl
Wed Mar 13 08:14:05 PDT 2013
On Wed, Mar 13, 2013 at 2:52 PM, Boris Zbarsky <bzbarsky at 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.
More information about the whatwg