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

Re: Update of RTCRtpSender "doohickey" proposal

From: Adam Bergkvist <adam.bergkvist@ericsson.com>
Date: Fri, 2 May 2014 12:51:11 +0200
Message-ID: <5363789F.7030401@ericsson.com>
To: Harald Alvestrand <harald@alvestrand.no>, <public-webrtc@w3.org>
On 2014-05-02 10:19, Harald Alvestrand wrote:
> On 05/02/2014 08:36 AM, Kiran Kumar Guduru wrote:
>> Samsung Enterprise Portal mySingle
>>
>> Perhaps this will avoid my confustion which I posted some time back [1].
>>
>> // parameter to the onaddtrack event
>>
>> interface RemoteTrackEvent : Event {
>>
>>  readonly attribute RtpReceiver receiver;
>>
>>  readonly attribute MediaStreamTrack track;
>>
>>  readonly attribute MediaStream stream;
>>
>> };
>>
>>
>> Is it required to have both stream and track?
>>
>> AFAIK stream contains track inside it.
>>
>> Is there any other requirement to have both track and stream
>> independently?
>>
>
> A stream can have multiple tracks. Without track, you don't know which
> track the event is on.
> A track can be in multiple streams. Without stream, you don't know which
> stream/track association the event concerns.

Of the three above, it's the MediaStreamTrack attribute that may be 
considered redundant since it can be accessed easily via receiver.track.

/Adam
Received on Friday, 2 May 2014 10:51:35 UTC

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