Re: [fetch] Aborting a fetch (#27)

> Is parent is cancelled before resolving, and you expected something to be logged, what would the value be?

The problem here is differing perspective and actor. I get the desire to want to cancel the `parent` and thus have that filter down to all observers not getting resolved (and perhaps getting instead notified of cancelation). I get, and want, cancelable `fetch(..)`. I also want cancelable `async function`, for the exact same reason.

What I am objecting to is the perspective that the code that creates `child1` gets to unilaterally decide that and affect the code that makes `child2`. Only the actor that created `parent` should get to decide that for all observers.

In `fetch(..)` context, the party that fires off the initial request should of course be able to decide later, "hey, forget that request." But downstream, if only one observer of that action (among many others) says "I don't care anymore, forget it", that should only allow that observer to cancel their observation, not affect other observers.

For example, one observer might say "I only wait a max of 3 seconds for a response, then I give up", but another observer may have a longer tolerance and want the request to keep going for awhile longer.

---
Reply to this email directly or view it on GitHub:
https://github.com/whatwg/fetch/issues/27#issuecomment-86999897