- From: aboba via GitHub <sysbot+gh@w3.org>
- Date: Sat, 24 Dec 2016 20:45:20 +0000
- To: public-webrtc-logs@w3.org
@alvestrand We describe the steps taken when transceiver.stop() is called, but do not yet describe the steps taken when setRemoteDescription(zeromlineOffer) is called. Some thoughts on what might happen: 1. Let transceiver be the RTCRtpTransceiver object corresponding to the zero'd m-line. 2. If transceiver.stopped is true, abort these steps. 3. Let connection be the RTCPeerConnection object corresponding to transceiver. 4. If connection's [[isClosed]] slot is true, abort these steps. 5. Let sender be transceiver.sender. 6. Let receiver be transceiver.receiver. 7. Stop sending media with sender. Send a BYE on all encodings. 8. Stop receiving media with receiver. 9, Set receiver.track.readyState to ended. Fire receiver.track.onended eventHandler. 10. Set transceiver.stopped to true. -- GitHub Notification of comment by aboba Please view or discuss this issue at https://github.com/w3c/webrtc-pc/issues/962#issuecomment-269099703 using your GitHub account
Received on Saturday, 24 December 2016 20:45:22 UTC