W3C home > Mailing lists > Public > public-webrtc-logs@w3.org > April 2017

Re: [webrtc-pc] "getParameters" and "setParameters" need more thorough specification

From: Bernard Aboba via GitHub <sysbot+gh@w3.org>
Date: Fri, 07 Apr 2017 05:39:20 +0000
To: public-webrtc-logs@w3.org
Message-ID: <issue_comment.created-292446048-1491543559-sysbot+gh@w3.org>
@taylor-b  One way to think about this is that there is a [[parameters]] internal slot that is distinct for the sender and receiver.  sender.setParameters() stores validated parameters in that slot and the getParameters() methods retrieve from it.  For the sender, setting the remote description stores into the [[parameters]] internal sender slot, and for the receiver, setting the local description stores into the [[parameters]] internal receiver slot. However, addTransceiver with sendEncodings or setCodecPreferences() does not store into the sender [[parameters]] internal sender slot (or the receiver slot).  Since sender.setParameters() cannot set the negotiation-needed flag (or the number of encodings), can the contents of the [[parameters]] internal slot affect createOffer() or createAnswer()?  I suspect the answer is "no". 

GitHub Notification of comment by aboba
Please view or discuss this issue at https://github.com/w3c/webrtc-pc/issues/1116#issuecomment-292446048 using your GitHub account
Received on Friday, 7 April 2017 05:39:26 UTC

This archive was generated by hypermail 2.4.0 : Saturday, 6 May 2023 21:19:40 UTC