- From: Jim Barnett <Jim.Barnett@genesyslab.com>
- Date: Fri, 31 May 2013 14:04:21 +0000
- To: Adam Bergkvist <adam.bergkvist@ericsson.com>, "robert@ocallahan.org" <robert@ocallahan.org>
- CC: Martin Thomson <martin.thomson@gmail.com>, "public-media-capture@w3.org" <public-media-capture@w3.org>
If a MediaStream received from a PeerConnection is immutable (I assume we're talking about the recipient of the call here), how can the recipient modify the call, e.g. by adding video to it? - Jim -----Original Message----- From: Adam Bergkvist [mailto:adam.bergkvist@ericsson.com] Sent: Friday, May 31, 2013 2:11 AM To: robert@ocallahan.org Cc: Martin Thomson; Jim Barnett; public-media-capture@w3.org Subject: Re: questions about direct assignment On 2013-05-31 02:11, Robert O'Callahan wrote: > That sounds good but WebRTC security stuff will need to be updated. I think we should pursue your (Robert's) idea [1] with two different types of MediaStreams; one type with immutable track lists that you get from gUM() and PeerConnection's "addstream" event, and one stream type that can be composed by the script. Then we can say that gUM() and PC-streams that have an initial origin and it will never change. Nice and simple. Composed streams doesn't originally have an origin but gets one from its contributing tracks. This is trickier, but you get that we you start composing streams yourself. /Adam [1] http://lists.w3.org/Archives/Public/public-media-capture/2013Apr/0127.html
Received on Friday, 31 May 2013 14:04:47 UTC