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

> 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

It does seem like this is a lot of complexity to expose for features that, although certainly important, aren't needed for many use cases. Using a different API for those with different exposed levers and dials provides the developer with a guarantee that the simple `fetch` case remains simple.

I've always felt that jQuery's `$.ajax` took the wrong approach by trying to force every server interaction down the same narrow API path via a big hairy set of input options that modify its behavior in drastic ways. It would be a shame to see `fetch` make the same mistake because, at least for now, it has avoided that trap.

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