W3C home > Mailing lists > Public > public-webapps@w3.org > October to December 2013

XMLHttpRequest and Fetch

From: Anne van Kesteren <annevk@annevk.nl>
Date: Tue, 22 Oct 2013 17:44:25 +0100
Message-ID: <CADnb78io2pF3Dh93WFohGwMkS9KPFnrKKoasQP911-hHK03-Yg@mail.gmail.com>
To: WebApps WG <public-webapps@w3.org>
http://xhr.spec.whatwg.org/ now uses http://fetch.spec.whatwg.org/
This was a fair amount of work and a trial for the other
specifications that have to move to Fetch at some point. I suspect
we'll need some convenience hooks for other specifications, as none
will be quite as complex as XMLHttpRequest.

Anyway, since this was a big change review is appreciated. If you
don't have time, just keep it in mind if you happen to look at it
later.

The idea here is to have all networking behavior centralized and not
scattered around and repeated for each individual end point. All APIs
(XMLHttpRequest, <img>, etc.) need to deal with redirects, HTTP
authentication, CORS, etc. and therefore having that defined in Fetch
makes a lot of sense. As with all architectural cleanup, this will
make extending things easier going forward.


-- 
http://annevankesteren.nl/
Received on Tuesday, 22 October 2013 16:44:54 UTC

This archive was generated by hypermail 2.3.1 : Friday, 27 October 2017 07:27:03 UTC