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

Agreed that ref count would be problematic for few reasons:

  * GC exposed and also unpredictable in its execution
  * `.then` is a pattern that favorites chainability and for some reason people love chainability, meaning it's not so easy to count down to zero within a chain, there'll always be someone at the end, unreferenced, and already attached, am I right? So how the initial fetch is supposed to abort since everyone unable to stop it can detach itself? Is is about getting rid of the initially assigned fetch? And what if I am an asshole that keeps one of the chained thenable referenced? Is everyone else screwed?

In any case, this perfectly summarizes my general disappointment with Fetch
> Fetch is an excellent example of an API that should not use Promises, because it involves the use of a scarce resource (ie connections).

But since we are here ... I guess it's too late so let's try to be pragmatic and cover as many cases as possible, keeping in mind the initial ease goal that was fetch.

Shall we?

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