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

To TL;DR my [last comment](https://github.com/whatwg/fetch/issues/447#issuecomment-270438848) a bit, we need to recognize that there are **four concerns** in play here, which I believe will be best served if they're recognized orthogonally:

- **Monitoring** an **incoming request** (in service workers)
- **Controlling** an **outgoing request**
- **Monitoring** an **incoming response** from an outgoing request
- **Controlling** an **outgoing response** (from an incoming request to a service worker)

Two of these concerns are about monitoring something out of the current code's control, two of these things are about controlling something the current code initiated, two of them are about requests, and two are about responses - but these are *four different cases*, and an appropriate design for any of these concerns needs to recognize which elements of the case it shares with which of its siblings.

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