- From: Travis Leithead <travis.leithead@microsoft.com>
- Date: Mon, 30 Jul 2012 17:20:22 +0000
- To: Stefan Hakansson LK <stefan.lk.hakansson@ericsson.com>, "public-media-capture@w3.org" <public-media-capture@w3.org>
> From: Stefan Hakansson LK [mailto:stefan.lk.hakansson@ericsson.com] > To me, the 'ended' on MediaStream level makes life easier for the application > developer. E.g., if the consent to use input devices is revoked by the user (I > imagine browsers will supply ways to do that), the app would know that directly > (and not have to keep track of that all tracks included in the MediaStream in > question have ended). > > But the problem that comes from being able to remove all tracks, and then add > (at least) one, was one I had not thought of before. In principle the same > problem would surface if all tracks of a MediaStream ended, and the > MediaStream went to state 'ended' as a result, followed by "add" of a non- > ended track. Another alternative is to simply enhance the MediaStream object with a corresponded "started" event for cases where a media stream with no tracks becomes a media stream with at least one live track.
Received on Monday, 30 July 2012 17:21:00 UTC