W3C home > Mailing lists > Public > public-webrtc@w3.org > January 2013

Re: ACTION-62, Priority API

From: Cullen Jennings (fluffy) <fluffy@cisco.com>
Date: Thu, 10 Jan 2013 17:42:54 +0000
To: Stefan Håkansson LK <stefan.lk.hakansson@ericsson.com>
CC: "public-webrtc@w3.org" <public-webrtc@w3.org>
Message-ID: <C5E08FE080ACFD4DAE31E4BDBF944EB113370B77@xmb-aln-x02.cisco.com>

On Jan 9, 2013, at 1:39 AM, Stefan Håkansson LK <stefan.lk.hakansson@ericsson.com> wrote:

> On 2013-01-09 04:11, Cullen Jennings (fluffy) wrote:
>> 
>> This seem far more flexible and complicated than needed. Lets just
>> set a constraint on the track to integer value from 1 to 3, or 1 to
>> 5
> 
> That is definitely the simplest approach.
> 
> pc.setPriority(track, value);
> 
> What I fear is that we will see the need for more and more settings down the road (setBitrate, setDTXOperation, ...), so if we use this approach I would prefer using constraints:
> 
> pc.applyConstraints(track, constraints);


That makes sense - I was trying to say that when I said set a constraint. 
Received on Thursday, 10 January 2013 17:43:21 UTC

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