On 4/21/14 2:47 PM, Martin Thomson wrote:
> 1. I think that this leaps to the conclusion that constraints are
> right without strong enough justification. Constrainable is a
> powerfully generic tool, and I'd want to see stronger evidence that a
> less generic mechanism is not going to work before I'd be happy with
> this.
+1. There's no Constrainable in the WebRTC spec anymore.
>> flow1.applyConstraints({bandwidth: 150-400, direction:sendonly,
>> simulcast-id:1, priortity:High});
>> flow2.applyConstraints({bandwidth:100-150, direction:sendonly,
>> simulcast-id:1});
>> flow4.applyConstraints({priority:Low});
Can't you just "set" these settings? i.e. no runtime arbitration between
multiple interests seems needed.
.: Jan-Ivar :.