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

[Bug 25497] RTCRtpSender / Receiver objects need to be added to the specification

From: <bugzilla@jessica.w3.org>
Date: Thu, 08 May 2014 06:06:33 +0000
To: public-webrtc@w3.org
Message-ID: <bug-25497-4991-F32M1cciFS@http.www.w3.org/Bugs/Public/>

--- Comment #1 from Harald Alvestrand <harald@alvestrand.no> ---
Summary from Justin Uberti, May 8:

Trying to bring this discussion to a conclusion... I sense consensus around the
- General concept of doohickeys, i.e. RTCRtpSender, RTPRtpReceiver.
- addTrack(track, streamId)/removeTrack and onaddtrack.
- Implicit cloning never occurs. This means that if you want to add a track
twice to a PC, you need to first clone it.

More discussion is still needed on:
- RTCRtpEncodingParams
- RTCDtlsTransport

Therefore I would like to advance the initial, uncontroversial parts of this
proposal, i.e. what I describe below. We can then discuss the exact nature of
the encodings and transport objects separately on the list, and at the interim

// the "send" doohickey

interface RTCRtpSender {

 readonly attribute MediaStreamTrack track;


// the "receive" doohickey

interface RTCRtpReceiver {

 readonly attribute MediaStreamTrack track;


// parameter to the onaddtrack event

interface AddTrackEvent : Event {

 readonly attribute RtpReceiver receiver;

 readonly attribute MediaStreamTrack track;

 readonly attribute MediaStream stream;


partial interface RTCPeerConnection {

// because a track can be part of multiple streams, the id parameter

 // indicates which particular stream should be referenced in signaling

 RTCRtpSender addTrack(track, streamId);  // replaces addStream; fails if
|track| has already been added                               

 void removeTrack(RTCRtpSender);  // replaces removeStream

 sequence<RTCRtpSender> getSenders();

 sequence<RTCRtpReceiver> getReceivers();

 EventHandler onaddtrack;  // replaces onaddstream; event object is

                                        // note that onremovestream is not
needed, since tracks are 'removed'

                                        // simply by progressing to the ENDED


You are receiving this mail because:
You are on the CC list for the bug.
You are the assignee for the bug.
Received on Thursday, 8 May 2014 06:06:34 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 19:17:58 UTC