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

Re: [Bug 15861] API for JS interaction with congestion control

From: cowwoc <cowwoc@bbs.darktech.org>
Date: Wed, 11 Sep 2013 01:43:41 -0400
Message-ID: <5230030D.5010607@bbs.darktech.org>
To: public-webrtc@w3.org
On 05/09/2013 1:01 AM, bugzilla@jessica.w3.org wrote:
> https://www.w3.org/Bugs/Public/show_bug.cgi?id=15861
> --- Comment #11 from Adam Bergkvist <adam.bergkvist@ericsson.com> ---
> (In reply to comment #9)
>> Another thing I wanted to clarify, when given conflicting constraints
>> (resolution, frame-rate, bitrate) does the browser get to decide which gets
>> priority over the other or does it fail-fast and notify the callback
>> immediately that the constraints cannot be honored as-is? In my proposal,
>> the latter occurs.
> It depends. Mandatory constraints are unordered, so when one fails the script
> gets notified. Optional constrains are ordered, so the script lists them in the
> order of importance.

     Why do you need mandatory constraints with the "fence" proposal? If 
the application is unwilling to accept the violation of some condition, 
it can abort the call. I don't think you gain anything by building this 
logic into the browser.

Received on Wednesday, 11 September 2013 05:44:26 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 19:17:50 UTC