- From: henbos via GitHub <sysbot+gh@w3.org>
- Date: Wed, 04 Jul 2018 08:12:03 +0000
- To: public-webrtc-logs@w3.org
Is the reason we set `currentDirection` ”late” - in the SLD(answer) as opposed to the SRD(offer) - because we want to give the client an opportunity to reject the transceiver? Two proposals and a question: 1. Is there any harm to set the `currentDirection` at SRD(offer) too? It can always be overridden at SRD(answer) if the client wants to do that. A small tweak would allow `currentDirection` to reflect if it is "active" or not. 2. Otherwise, add `isReceiving` to receiver which is essentially set to (currentDirection == 'sendrecv' || currentDirection == 'recvonly') except we also set it to true at SRD(offer) when the remote side has offered to send us something on that receiver, but before we have set the answer to make that decision final. Question: Is the receiver able to receive as soon as you do SRD(offer), or will receiving not happen until later? At SLD(answer)? When the answer has been signaled to the remote endpoint? -- GitHub Notification of comment by henbos Please view or discuss this issue at https://github.com/w3c/webrtc-pc/issues/1920#issuecomment-402400257 using your GitHub account
Received on Wednesday, 4 July 2018 08:12:15 UTC