W3C home > Mailing lists > Public > public-webrtc@w3.org > May 2014

Re: Next steps on RTCRtpSender "doohickey" proposal

From: Harald Alvestrand <harald@alvestrand.no>
Date: Thu, 08 May 2014 13:13:36 +0200
Message-ID: <536B66E0.3040809@alvestrand.no>
To: public-webrtc@w3.org
On 05/08/2014 12:34 PM, Kiran Kumar Guduru wrote:
>
> In spec it is specified that mediaStream ids may  be duplicated.
>
> "The id of a |MediaStream 
> <http://dev.w3.org/2011/webrtc/editor/webrtc.html#dfn-mediastream>| 
> object is unique to the source of the stream, but that does not mean 
> it is not possible to end up with duplicates."
>
> In this scenario,
>
> How to differentiate two streams with same Id?
>

Are you talking about the perspective of a Javascript programmer, or the 
perspective of a browser writer?

The case where it can occur is if you get the same stream (same ID) via 
two different PeerConnections, or get your own streams reflected back at 
you.

I'm not sure it's a problem for the Javascript programmer. But it argues 
for stating the addtrack API in terms of stream objects, not stream IDs 
(since there may be two objects with the same ID).
Received on Thursday, 8 May 2014 11:14:06 UTC

This archive was generated by hypermail 2.3.1 : Monday, 23 October 2017 15:19:40 UTC