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

> I understand the controller is for cancellation, but at first blush I have no idea what a "fetchObserver" is

The controller is for making to changes, and the observer is for observing changes. So:

* "I want to change the priority of this fetch" - method on the controller.
* "Is the state of this fetch completed/abort/in progress?" - method on the observer.
* "Has this fetch changed priority?" - listener on the observer.
* "Has this fetch been aborted?" - listener on the observer.
* "I want to abort this fetch" - method on the controller.
* "I want to hear about upload progress" - listener on the observer.

The intent here is to provide means of observing fetches without being able to control them. Developers have asked for this distinction, and it's also needed within a service worker.

-- 
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-281313065