Re: [whatwg/dom] Abort controller design (#438)

> Currently we just pass the underlying request/response across threads, which is somewhat similar to passing JavaScript records across, although streams made that less ideal.

Right. To be clear the steps around 10.3.1.2.5 in https://w3c.github.io/ServiceWorker/#fetch-event-respondwith are what I'm referring to. They are very similar to what transferring a stream will eventually look like (at least for byte streams), and so we could probably shorten them greatly by factoring out "transfer a stream". And then probably "transfer a stream" will also be used to allow structured transfer of the stream.

---

However I realized that in order to make fetch() abortable we're going to need to store the abort signal in the stream after all, if we want the abort signal to control both the initial headers request and the body. So we will need to define transferring/cloning of AbortSignals in order to define transferring of streams.

-- 
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/438#issuecomment-302155376