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

[Bug 15861] API for JS interaction with congestion control

From: <bugzilla@jessica.w3.org>
Date: Wed, 04 Sep 2013 13:03:29 +0000
To: public-webrtc@w3.org
Message-ID: <bug-15861-4991-cSeDINMQd5@http.www.w3.org/Bugs/Public/>
https://www.w3.org/Bugs/Public/show_bug.cgi?id=15861

--- Comment #9 from Gili <cowwoc@bbs.darktech.org> ---
(In reply to comment #7)
> The general mechanism you describe here is pretty much how our current
> constraint approach work (as far as I understand it).

One difference I note is the existence of mandatory constraints in the spec. In
my proposal, all constraints are optional and the application decides what to
do when a constraint cannot be honored.

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.

I'm trying to push as much of the decision-making out of the browser and into
the application's hand.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
You are the assignee for the bug.
Received on Wednesday, 4 September 2013 13:03:37 UTC

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