Re: [whatwg/dom] Consider adding AbortController.prototype.follow(signal) (#920)

Hey, a few of us have been discussing this a lot and we think there needs to be a way for signals to "follow" other signals. This is because making linked signals is _very_ hard at the moment.

This is [impossible to do in userland](https://github.com/nodejs/node/issues/35990#issuecomment-723154000) though I'll let Brian leave a more detailed comment.

Node is very interested in this API and I believe it is very hard to use AbortSignal for large web apps with "linked signals" without it. The use case we've seen over and over is something like [this one](https://github.com/benjamingr/cancellation-use-cases/blob/main/use-cases/01-server-process-request.md) - I've actually seen this in browser environments and converted it to a Node case for our meeting :]

Regarding the color of the bike shed: Is there any reason this is `AbortController.prototype.follow(signal)` and not `new AbortController(...signals)`?




-- 
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/dom/issues/920#issuecomment-726878717