- From: Harald Alvestrand via GitHub <sysbot+gh@w3.org>
- Date: Tue, 19 Jan 2021 08:25:03 +0000
- To: public-webrtc-logs@w3.org
It's not clear to me what "not as safe as" refers to here - what's the threat model that makes this a safety difference? The point of doing the decoupled model is that the result of consuming a ReadableStream does *not* need to be a WritableStream, and the source of a WritableStream does *not* need to be a ReadableStream; one can construct these from any source. This is important for several applications, including using WebCodecs to encode/decode, and for using other transports than PeerConnection to move data around. -- GitHub Notification of comment by alvestrand Please view or discuss this issue at https://github.com/w3c/mediacapture-insertable-streams/issues/4#issuecomment-762682129 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Tuesday, 19 January 2021 08:25:04 UTC