W3C home > Mailing lists > Public > public-webrtc@w3.org > November 2016

[webrtc-pc] Review use of "stopped"

From: aboba via GitHub <sysbot+gh@w3.org>
Date: Fri, 04 Nov 2016 16:55:43 +0000
To: public-webrtc@w3.org
Message-ID: <issues.opened-187385377-1478278541-sysbot+gh@w3.org>
aboba has just created a new issue for 
https://github.com/w3c/webrtc-pc:

== Review use of "stopped" ==
The following references to "stopped" RtpSender/RtpReceivers need to 
be reviewed:

1. Definition of close(): 
All RTCRtpSenders in senders are now considered stopped.
All RTCRtpReceivers in receivers are now considered stopped.
Can we reformulate this by setting  RTCRtpTransceiver.stopped to true?

2. replaceTrack:
If sender is stopped, return a promise rejected with an 
InvalidStateError.
Could this be reformulated by testing if transceiver.stopped is true?
  

3. insertDTMF:
If sender has been stopped, throw an InvalidStateError exception.
If sender has been stopped, abort these steps.
Could this be reformulated by testing if transceiver.stopped is true 
or if transceiver.direction is recvonly?

Please view or discuss this issue at 
https://github.com/w3c/webrtc-pc/issues/917 using your GitHub account
Received on Friday, 4 November 2016 16:55:49 UTC

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