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

I honestly don't see any concrete/practical difference in having a `.cancel` method VS exposing externally the private cancel callback. However, I think I agree the controller seems to be a cleaner way.

What I also start noticing is that this supposed to simplify basic cases but it starts looking more complex at every re-iteration even at its roots.

I start wondering if we should leave fetch as it is and confine its usage for quick/small exchanges, advocating Streams for all those case where "real abortability" is needed like a gmail file attachment, a download, or anything bigger than "n" KB

A comment, a Tweet, an asset, a like/fave/reply ... these are all small valid use cases that would benefit fetch, but then I'd see it as over-engineered if that would be its domain of usage.

Apologies for the loud thinking

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