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

[webrtc-pc] How does setDirection interact with active/inactive sender/receivers?

From: Daniel Burnett via GitHub <sysbot+gh@w3.org>
Date: Thu, 16 Jun 2016 13:28:07 +0000
To: public-webrtc@w3.org
Message-ID: <issues.opened-160661583-1466083686-sysbot+gh@w3.org>
burnburn has just created a new issue for 
https://github.com/w3c/webrtc-pc:

== How does setDirection interact with active/inactive 
sender/receivers? ==
The description of setDirection says
"The setDirection method sets the direction of the RTCRtpTransceiver. 
Calls to setDirection() do not take effect immediately. Instead, 
future calls to createOffer and createAnswer mark the corresponding 
media description as sendrecv, sendonly, recvonly or inactive as 
defined in [JSEP] (section 5.2.2. and section 5.3.2.). Calling 
setDirection() sets the negotiation-needed flag."

However, there is no mention of setDirection anywhere in JSEP.  In 
fact, section 5.2.4 
(https://rtcweb-wg.github.io/jsep/#rfc.section.5.2.4) explains how 
sender/receiver (in)activity sets this value.  How does setDirection 
interact with what is described in JSEP?

This is a work item of issue #337.

Please view or discuss this issue at 
https://github.com/w3c/webrtc-pc/issues/706 using your GitHub account
Received on Thursday, 16 June 2016 13:28:08 UTC

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