Re: [whatwg/streams] Communication between workers/windows via Streams API (#244)

Yeah, that makes sense. I was focusing on the opposite case, transferred ReadableStreams, where the source enqueues things and it would be cloned/serialized synchronously at enqueue time. But yeah, for a transferred WritableStream, it would be like you said. The destination realm would be enqueueing things at writer.write time, and ending up in the queue at the underlyingSink's thread, where the stream was first constructed.

-- 
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/streams/issues/244#issuecomment-257181106