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

> Imagine foo is in some library written by someone else. This is exactly what action at a distance is.

No, I don't understand - why? If someone changes the code at a distance to behave differently _of course_ you get action-at-a-distance. The point is that the semantics of _your code_ don't change, the same paths still get executed regardless of how the code was changed at `foo`, that's not the situation with any other semantics for cancellation of fetch and half the point of disinterest semantics. 

> Independent of this argument, I think it's a fallacy to suggest that clients only care about their callbacks. This assumes functions without side-effects.

As far as I understand no one is suggesting that though. 

. 

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