Re: [whatwg/fetch] Aborting a fetch: The Next Generation (#447)

> 3 different consumers of the same promise can be affected by only one of them deciding to cancel it.

This would only be true if someone composed all of the cancellation through in this manner. It rarely makes sense to compose cancelation through in this way when multicasting. Any cancellation of a multicast type (like a promise) would require refCounting. Which would live internally in that returned promise.

This would easily be the most ergonomic solution for everyone. It's also a solution that's detectable from a single passed value, which is useful for libraries like Rx and others. 

-- 
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/447#issuecomment-275229547