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

@getify so, (subclass) CancelablePromise also will be affected by "action at a distance" concern, right? Then how it matters which class it will be, CancelablePromise or just Promise?
Also, in my mind, everything that exposes cancel-ability to outside world will be affected by "action at a distance" thing including xhr, tasks, promises with cancelable token, etc. Once you provide cancel-ability to outside world you are affected, no matter what you are using. So if you do not want to be affected, then just do not provide that ability.

This is the only reason I see for not updating Promise class itself, but introducing CancelablePromise because in theory you should be able to cast it to regular Promise and return promise without cancel-ability. But wait, hmm.. every fetch req will have that man in a distance -- the browser with a user as a driver which may hit "stop" at any time.
I never had situation where I shared cancelable action to other part of code and that code accidentally canceled that action. If someone are dealing with cancelable action then one should be aware by default what cancel may occur, especially with network request where are not only one participant.



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