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

Re: Missing Features: Stream Control

From: Adam Roach <adam@nostrum.com>
Date: Fri, 18 Oct 2013 12:13:17 -0500
Message-ID: <52616C2D.9040208@nostrum.com>
To: Aymeric Vitte <vitteaymeric@gmail.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>
On 10/18/13 11:56, Aymeric Vitte wrote:
> Regarding your proposal I was about to propose to add about the same 
> thing in Streams: at least a stop method (which would send an EOF) and 
> maybe a resume method, or something like your pause/unpause.

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.

Received on Friday, 18 October 2013 17:13:57 UTC

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