- From: Ian Hickson <ian@hixie.ch>
- Date: Mon, 4 Mar 2013 20:14:05 +0000 (UTC)
- To: Anne van Kesteren <annevk@annevk.nl>
- Cc: WHATWG <whatwg@whatwg.org>
On Mon, 4 Mar 2013, Anne van Kesteren wrote: > > So in the grand rewrite of fetch I wonder: > > 1) How does HTML distinguish for which fetch the tasks are queued? How do you mean? > 2) How do we deal with tasks for uploading data? Currently fetch only > deals with processing incoming data, not outgoing. Why would you need tasks for uploading? > In both these cases, how do we either allow the caller to filter or > filter for caller? Not sure what you mean. > 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. Doesn't the current prose already handle all this? > Also, is the networking task source exclusively used for fetch? Should > we rename it then (harhar)? It's used by various things, seach for "is the networking task source" in the HTML spec. e.g. "update the session history with the new page" uses it. Basically, anything that needs to be ordered relative to network activity rather than DOM activity. -- Ian Hickson U+1047E )\._.,--....,'``. fL http://ln.hixie.ch/ U+263A /, _.. \ _\ ;`._ ,. Things that are impossible just take longer. `._.-(,_..'--(,_..'`-.;.'
Received on Monday, 4 March 2013 20:14:33 UTC