Re: [whatwg/streams] Editorial changes to transferable streams explainer (#977)

I was a little concerned that Transferable Streams would make it pretty easy to route data around the cross-origin restriction, but I don't think this feature makes it much worse than it already is--namely, today an origin A can postMessage the received chunks from a ReadableStream to origin B's message handler. With this feature, only one postMessage is needed to pass the Stream, and then origin B can drink from the pipe for as long as it likes.

I do think the explainer needs to support a better use-case than the general "workers make things easier", or "delegation is good". After all, the workaround for not having this feature is really trival--just make the request for Stream in the Worker/Frame instead (so the transfer is unnecessary). What are the use-cases where the Worker/Frame would be unable to implement that workaround? Why? (The only cases I can imagine are to enable easier cross-origin information sharing on the client.)

-- 
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/pull/977#issuecomment-454575226