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

@mariusGundersen 

> This is exactly why I think it should be called an IgnorablePromise and should have an ignore method, rather than an abort or cancel method

Hm, I think "cancel" is better than "ignore" as the latter doesn't suggest that the underlying operation may cease. Whereas "cancel" can be "cancel my observation" and "cancel the underlying behaviour". Anyway, I'd rather get consensus on the feature design before bikeshedding naming.

> If you have a promise that you need to give to multiple consumers, then you should clone it, just like you have to clone the request/response of fetch.

Yep, if you want to retain cancellation but vend a child promise, it's simply `cancellablePromise.then()`. If you don't want cancellation it's `Promise.resolve(cancellablePromise)`.

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