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

> changes to "improve" fetch may lead us right back into a single complex API.

That seems like an unfounded concern. Nothing being described here remotely resembles the `$.ajax({ .. })` complexity.

1. If as my earlier message suggested the return value from `fetch` is a single object with only two members, the `promise` and the `cancel(..)` method, the only "extra" complexity to the non-cancel use-case is a `.promise` added into the chain.
2. If promises are extended to have a `cancel(..)` or `abort(..)` method (ugh), then no additional complexity is added to the non-cancel use-case.
3. If we go the cancel-token route, that's actually the most additional complexity, which amounts to a single extra argument to `fetch(..)`.

None of that sounds like `$.ajax` -> `options` to me.

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