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

I feel kind of strongly we should just allow `postMessage()` of the `ReadableStream`.  I thought we had preliminary agreement to this affect in #276.

If someone wants a WritableStream they should be able to create an identity transform, write to it, and then postMessage() the readable side.

I still like just requiring postMessage() to lock the ReadableStream and then drain the underlying source as mentioned in:

   https://github.com/whatwg/streams/issues/276#issuecomment-90238722

This lets the browser grab a c++ underlying source and optimize off thread, but also works for js underlying sources.  Interposing a writable step seems like it would make this harder, not easier.

---
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-228099191