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

Re: Missing Features: Stream Control

From: Aymeric Vitte <vitteaymeric@gmail.com>
Date: Fri, 18 Oct 2013 19:47:35 +0200
Message-ID: <52617437.4070005@gmail.com>
To: Adam Roach <adam@nostrum.com>, "public-webrtc@w3.org" <public-webrtc@w3.org>, "Web Applications Working Group WG (public-webapps@w3.org)" <public-webapps@w3.org>, Takeshi Yoshino <tyoshino@google.com>, Feras Moussa <feras.moussa@hotmail.com>

Le 18/10/2013 19:13, Adam Roach a écrit :
> To be clear, the .enabled flag and .stop() method are already there, 
> and they already pause/unpause the stream and tear it down, 
> respectively. I'm just proposing concrete semantics for how they 
> interact with any PeerConnection that the track is associated with.

But they are not in the Streams proposal, see my other answer.

Peersm : http://www.peersm.com
node-Tor : https://www.github.com/Ayms/node-Tor
GitHub : https://www.github.com/Ayms
Received on Friday, 18 October 2013 17:48:06 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 19:17:51 UTC