Re: [webrtc-pc] What direction should a stopped transceiver have? #661 (#2479)

The [[CurrentDirection]] slot reflects what has been negotiated in SDP, meaning any of the values "sendrecv", "sendonly", "recvonly", "inactive", or if negotiation has not happened we use the value null.

Note that "stopped" is _not_ a direction that is used in SDP, it's something that we invented in webrtc-pc.

This is why currentDirection is implemented as:

- If transceiver.[[Stopped]] is true, return "stopped".
- Otherwise, return the value of the [[CurrentDirection]] slot.

This means that editorial-wise, we have two variables to represent a single state (currentDirection). Implementation-wise, it would probably be equally valid to have a single state (currentDirection) that also includes the value "stopped".

-- 
GitHub Notification of comment by henbos
Please view or discuss this issue at https://github.com/w3c/webrtc-pc/issues/2479#issuecomment-589167932 using your GitHub account

Received on Thursday, 20 February 2020 16:29:03 UTC