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

Just chiming in that all of our UIs at Netflix have used a system similar to @jhusain's Task proposal for the past few years, and it's been exceptionally effective and scalable.  It provides both explicit cancellation of the fetch if it's needed, as well as automatic cancellation if everyone stops listening.

The important distinction from Promise is that .then on a Task describes a data transformation without adding a listener for the result.  You need to call .get providing callbacks for result/error if you want to start listening.  Promises conflate the two actions, which means it's not possible to tell when consumers no longer care about completion.

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