True,

RTCRtpReceiver consists of only one track.

Seems we can remove the track attribute to avoid redundancy.

 

Kiran.

 

------- Original Message -------

Sender : Adam Bergkvist<adam.bergkvist@ericsson.com>

Date : May 02, 2014 19:51 (GMT+09:00)

Title : Re: Update of RTCRtpSender "doohickey" proposal

 

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