- From: James M Snell <notifications@github.com>
- Date: Sat, 18 Dec 2021 09:08:38 -0800
- To: whatwg/dom <dom@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Saturday, 18 December 2021 17:08:51 UTC
Just an update on this... we recently just landed early support for this in Node.js. When sending an `AbortSignal` over postMessage, a new `AbortSignal` is created on the receiving end connected to the original via a `MessagePort`. When the original signal is triggered, it has an abort algorithms that sends a message over the `MessagePort` that triggers the other. Very simple and straightforward. The key caveat is that there is some latency between when the original `AbortSignal` is triggered and when the newly created one is triggered due to the message passing infrastructure (in Node.js there's one event loop turn required) -- Reply to this email directly or view it on GitHub: https://github.com/whatwg/dom/issues/948#issuecomment-997231941 You are receiving this because you are subscribed to this thread. Message ID: <whatwg/dom/issues/948/997231941@github.com>
Received on Saturday, 18 December 2021 17:08:51 UTC