Gray Zhang (2015-03-02T14:32:34.000Z)
d at domenic.me (2015-03-27T23:59:23.540Z)
+1 to the ignore term, I’ve opened an issue about it in https://github.com/promises-aplus/cancellation-spec/issues/14 IMO the term cancel(or abort) and ignore are totally different things, the former one means “do not continue, stop it right now” and the “stop” state should be broadcast to everyone who is interested in the work, while the latter means “I don’t care about the result anymore, just play it as you like”, it means the async progress can be continued In practice both scenario are commonly seen, we may abort a resource fetch in order to save bandwidth and opened connections, or we may in other side just ignore it since continue to complete the fetch can result in a local cache, which speeds up our fetch next time Back to the ignore scenario, there is still some confusion left for me: Should ignore be a individual behavior, or a global one. This means should we just be able to “ignore” one callback, or just take a promise to a “ignore” state in which all callbacks are revoked Should later then calls be aware that the promise is already ignored, or ignorance should be completely transparent to clients (which means all later then are effortless)