W3C home > Mailing lists > Public > public-media-capture@w3.org > April 2013

Re: addTrack/removeTrack on gUM streams and PeerConnection remote streams

From: Robert O'Callahan <robert@ocallahan.org>
Date: Wed, 17 Apr 2013 22:23:24 +1200
Message-ID: <CAOp6jLbtCYkobq1yJHwMQwAvRb_+Uu0tnxMBnf-DLamaj9=DRg@mail.gmail.com>
To: Adam Bergkvist <adam.bergkvist@ericsson.com>
Cc: Stefan Håkansson LK <stefan.lk.hakansson@ericsson.com>, "public-media-capture@w3.org" <public-media-capture@w3.org>
On Wed, Apr 17, 2013 at 10:18 PM, Adam Bergkvist <
adam.bergkvist@ericsson.com> wrote:

> Since they're only used to listen to when the UA updates the track set
> they wouldn't be used when it's only the application that manages the track
> set.
>
> This is a bit confusing in the current spec. The description of the events
> say that they are fired whenever a track is added, which is misleading
> since they are not fired in the addTrack()/removeTrack() algorithms. It's
> fixed for the next release.
>

We should also fire them when addTrack()/removeTrack() are called,
shouldn't we?

Rob
-- 
q“qIqfq qyqoquq qlqoqvqeq qtqhqoqsqeq qwqhqoq qlqoqvqeq qyqoquq,q qwqhqaqtq
qcqrqeqdqiqtq qiqsq qtqhqaqtq qtqoq qyqoquq?q qEqvqeqnq qsqiqnqnqeqrqsq
qlqoqvqeq qtqhqoqsqeq qwqhqoq qlqoqvqeq qtqhqeqmq.q qAqnqdq qiqfq qyqoquq
qdqoq qgqoqoqdq qtqoq qtqhqoqsqeq qwqhqoq qaqrqeq qgqoqoqdq qtqoq qyqoquq,q
qwqhqaqtq qcqrqeqdqiqtq qiqsq qtqhqaqtq qtqoq qyqoquq?q qEqvqeqnq
qsqiqnqnqeqrqsq qdqoq qtqhqaqtq.q"
Received on Wednesday, 17 April 2013 10:23:53 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 21:24:40 UTC