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

[whatwg] Fetch: networking tasks

From: Anne van Kesteren <annevk@annevk.nl>
Date: Mon, 4 Mar 2013 16:57:19 +0000
Message-ID: <CADnb78jPxwuUk0rGqNiqJ9qu5Ly0Ww5atRYvd_Rkt6qj2G5S5Q@mail.gmail.com>
To: WHATWG <whatwg@whatwg.org>
So in the grand rewrite of fetch I wonder:

1) How does HTML distinguish for which fetch the tasks are queued?

2) How do we deal with tasks for uploading data? Currently fetch only
deals with processing incoming data, not outgoing.

In both these cases, how do we either allow the caller to filter or
filter for caller? Caller APIs are generally not interested in
redirects, e.g. progress events are for the response entity body, not
any number of redirects that preceded receiving that. Upload progress
events are only ever transmitted after a CORS preflight completed.

Also, is the networking task source exclusively used for fetch? Should
we rename it then (harhar)?

Received on Monday, 4 March 2013 16:57:47 UTC

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