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

> But can we all agree at least of basic concept things 

You purport to describe things in basic concepts, but then you choose a specific solution (promise instance cancelation) for all your assumptions. I object. Not that my objection carries any weight.

My summary of "basic concept things" that seems more sensible and less limiting would be:

* `fetch(..)` should be cancelable in some way, and that cancels the **request** and any **response** "observers".
* If the `fetch(..)` action is canceled, the entire down-stream chain of its promises must be canceled/aborted/rejected/etc, not just the first level. Ideally this cancelation would be observable down-stream (either as a rejection or as a third state).
* The cancelation capability should be something that can be passed along to (aka, made available to) all places where the promise-for-response would be passed, whether that be as separate values, combined in a single object, or combined into promises. (this relieves the pressure of having any down-stream observer automatically be able to affect its peers at a distance, but lets them be granted this capability if desired)
* Should make sense, and be equally effective, with `async / await` and any other (future) language mechanism that either explicitly or implicitly creates promises to represent the completion of a task.


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