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

@jan-ivar the repository is called Cancelable promise but it's not actually about promise cancellation. It's about third state semantics.

What we're looking at is https://github.com/zenparsing/es-cancel-token 

Honestly I still think that promise cancellation works just fine and so do thousands of others who use it in production (no action at a distance). Apparently the language TC wanted to get things to a point where everything is cancelled the same way (through cancellation tokens). So we're very likely to see:

    fetch(request, token)

Where you cancel the token and the cancellation capability is passed separately. 

Please do drop by https://github.com/zenparsing/es-cancel-token and leave feedback - lots of ideas being tossed around. As for https://github.com/domenic/cancelable-promise it deals with what happens after the token is activated - we need cancellation semantics that are not abortive semantics so in a way we both win in some parts. 

I get non-abortive sound cancellation semantics and you get tokens instead of `cancel` on a promise.


---
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/whatwg/fetch/issues/27#issuecomment-227481731