Add activateReceiver method to RTCRtpTransceiver #505
Conversation
Related to Issue #473
aboba
changed the title
|
@pthatcherg Can you review? |
|
|
||
| <p>If the receiver is not already active and the PeerConnection is in the stable state, | ||
| this will set the <code>negotiationneeded</code> flag. | ||
| </dd> |
There was a problem hiding this comment.
I was hoping we would need only one "set horrible" (activateSender()) and not two (activateReceiver()).
Does this accomplish anything other than a way to tell the sending side "please stop sending me this track" without rejecting the whole m-line?
There was a problem hiding this comment.
If we need it, this PR looks good.
|
Implementing various "hold" scenarios appears to require both "set horrible" methods. For example, if addTransceiver(init) is called with init.send=true and init.receive=false (e.g. sendonly), activateReceiver() can be used to go from sendonly to sendrecv, taking the remote peer off hold (after another O/A exchange). See the "hold" example, in http://tools.ietf.org/html/rfc4317 Section 3.1. |
Add activateReceiver method to RTCRtpTransceiver
Add activateReceiver method to the RTCRtpTransceiver
Related to Issue #473