Re: [whatwg/fetch] Aborting a fetch: The Next Generation (#447)

I think there's a strong argument for having something that represents the ongoing fetch:

* Cancelation should affect the overall fetch, not the request.
* Observing cancelation state and done state through getters.
* The additional use cases centered around fetches (push, changing priority on the fly, observing progress).

Putting that on Request would get quite ugly. (Especially considering the Cache API and short lifetime of Request objects (`fetch()` creates a new one from the one it is passed).)

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/whatwg/fetch/issues/447#issuecomment-270609915