[Bug 27227] New feature: Track swapping

https://www.w3.org/Bugs/Public/show_bug.cgi?id=27227

Martin Thomson <martin.thomson@gmail.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |martin.thomson@gmail.com

--- Comment #1 from Martin Thomson <martin.thomson@gmail.com> ---
Note that the mutable attribute was not popular.  There was a general
preference for a setter.  The primary reason being that the replacement might
fail.

I think that the general sense was that failure was not a problem that browsers
need concern themselves with: the track would simply go BYE-BYE (i.e., RTCP
BYE) if media could not be provided in a compatible form from the new source. 
However, it was observed that replacement would not be atomic and that maybe a
promise-bearing method was superior.  That would allow for the time of
replacement to be marked, as well as giving the application a way to learn
about errors.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
You are the assignee for the bug.

Received on Monday, 3 November 2014 23:25:50 UTC