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

> wait just a tiny second @benjamingr : what if once canceled the then() won't return a cancelable Promise anymore? Or you just don't want to deal with any sort of cancellable chain at all?

>From what I can tell - not having a cancellable chain avoids all the issues raised here (and those raised by Kris) completely and solves the most common use case of just aborting a request. It does not require promise specification support either - there are no conflicts or aggregation issues either.

I'm not convinced this is the right approach. Basically what I'm looking for is to be sold on why chaining and aggregation is important enough to require dealing with semantics like reference counting (ala what Jake's API), termination rather than cancellation (ala NekR's proposal) suggested or library-like cancellation (ala your gist). 



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