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

RE: Issue 497: RID as read-only in setParameters()?

From: Mathieu Hofman <Mathieu.Hofman@citrix.com>
Date: Thu, 11 Feb 2016 19:52:27 +0000
To: Adam Roach <adam@nostrum.com>, Bernard Aboba <Bernard.Aboba@microsoft.com>, Jan-Ivar Bruaroey <jib@mozilla.com>, "public-webrtc@w3.org" <public-webrtc@w3.org>
Message-ID: <da5d108599b446cbb69524d0ba4c141c@SJCPEX02CL03.citrite.net>
From what I understand of the problem, you can only provide a new value for RID if there wasn’t a value before, i.e. the whole encoding didn’t exist.

Semantically it sounds more like a write-once than a read-only?

Mathieu

From: Adam Roach [mailto:adam@nostrum.com]
Sent: Thursday, February 11, 2016 11:40
To: Bernard Aboba <Bernard.Aboba@microsoft.com>; Jan-Ivar Bruaroey <jib@mozilla.com>; public-webrtc@w3.org
Subject: Re: Issue 497: RID as read-only in setParameters()?

On 2/11/16 13:34, Bernard Aboba wrote:

Your example does however point out the need for clarity with respect to the meaning of “read only”.

And we're going to want to distinguish between:

- Values chosen by the browser that cannot be influenced by the application (e.g., SSRC), and
- Values chosen by the application that cannot be changed once a session is in progress (e.g., RID)

/a
Received on Thursday, 11 February 2016 19:55:33 UTC

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