- From: <bugzilla@jessica.w3.org>
- Date: Wed, 04 Sep 2013 05:14:23 +0000
- To: public-webrtc@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=15861
Adam Bergkvist <adam.bergkvist@ericsson.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |adam.bergkvist@ericsson.com
--- Comment #7 from Adam Bergkvist <adam.bergkvist@ericsson.com> ---
(In reply to comment #6)
> [...]
> This approach is not specific to congestion control. It can be applied to
> all other constraints as well.
The general mechanism you describe here is pretty much how our current
constraint approach work (as far as I understand it).
A "fence conditions" is represented by a MinMaxConstraint object [1]. The
script will be notified when the browser cannot stay within the fence via the
"overconstrained" event [2].
[1]
http://dev.w3.org/2011/webrtc/editor/getusermedia.html#idl-def-MinMaxConstraint
[2]
http://dev.w3.org/2011/webrtc/editor/getusermedia.html#event-mediastreamtrack-overconstrained
--
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 05:14:24 UTC