- From: Martin Thomson via GitHub <sysbot+gh@w3.org>
- Date: Mon, 10 Jul 2017 00:10:47 +0000
- To: public-webrtc-logs@w3.org
To @aboba's question, yes, you could set it later, but only if it agrees with the current target peer identity. So the challenge with `setConfiguration()` is that it can be called after the session is established. If the current peer is unidentified, then we have a problem because the session now disagrees with the configuration. It seems like the right solution here is to define an internal slot `[[TargetPeerIdentity]]`, which can three states: unspecified, null, and a string value. This is initially unspecified. Specifying a value using `setConfiguration()` sets the value to null/string. Connecting sets the value to null/string. If `setConfiguration()` attempts to set a value and it isn't either the same as the current value, or the current value is unspecified, then `setConfiguration()` fails. The same process applies when connecting. -- GitHub Notification of comment by martinthomson Please view or discuss this issue at https://github.com/w3c/webrtc-pc/issues/1456#issuecomment-313974817 using your GitHub account
Received on Monday, 10 July 2017 00:10:52 UTC