Yeah, you can work on this :) I really wanted to work on this but as Josh said I have a million other things to do.

I personally would wait for @jdm's async net changes to land, but you can incrementally implement most of Fetch beforehand, especially the little bits and pieces like is_simple_method(), is_simple_header() (and all of the stuff like redirect handling, etc). You can also just go ahead and implement it with the intention to make it work with async net changes later. Either works.

Just to give a broad overview of what a completed version:

Most of fetch.spec.whatwg.org to be implemented in the fetch module in net. It should be structured similar to how the spec is structured, so that updates to the spec can be reflected easily.
Extremely little CORS code in script. cors.rs should die
Extremely little Fetch code in script. XHR should contain all the stuff on xhr.spec.whatwg.org, and whenever it says "Fetch foo", that should just be implemented as a call into net::fetch or something. Of course, post the async net changes it might be slightly more complicated than that, but basically we want very little net code in script.
Ideally the Fetch API would be generic -- so features of the API which XHR (our only consumer of fetch right now) doesn't use should still be implemented as much as possible. Eventually stuff like img and iframe will be using Fetch (as well as fetch()) spec-wise, so we want them to be able to reuse the same code.

Mostly it is straightforward, since the spec is pretty clear cut. Spec questions can go to annevk in #whatwg (on Freenode). The hard part is figuring out how to make it interface with the rest of the code -- XHR and other things need to be able to consume the data as it comes in, so we need some sort of pipelining. The resource task already provides channels on which to listen to for bits of data, so we could use the same design, but again, jdm's async changes provide a better (but more confusing) API so you should probably use that.

Feel free to ask any further questions!

Uh oh!

Implement the Fetch specification: infrastructure. #4576

Description

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions