RE: Transport control API

> -----Original Message-----
> From: Harald Alvestrand [mailto:harald@alvestrand.no]
> Sent: den 16 oktober 2013 16:57
> To: public-webrtc@w3.org
> Subject: Re: Transport control API
> 
> On 10/15/2013 08:51 PM, Göran Eriksson AP wrote:
> >
> >> 15 okt 2013 kl. 17:28 skrev "Harald Alvestrand" <harald@alvestrand.no>:
> >>
> >> This has been quiet for a while.
> >>
> >> I'm not happy with the name (it's not a transport), but I haven't
> >> heard a better one.
> >>
> >> But what else could we call it? MediaTrackTransmissionController?
> > Not bad as start...
> >
> > BTW- should there not be something on the PeerConnection level as well?
> I have forgotten if we reached a consensus on that part previously...
> 
> Yes, PeerConnection's constructor takes constraints, so it should also
> implement the Constrainable interface.
[GAPE:] I assume this implies we need to add to the WebRTC API draft how to use Constrainable for managing the transmitted bitrate on PeerConnection. Anyone has that task/ACTION?


> 
> >
> > Göran
> >
> >
> >
> >>
> >>> On 09/05/2013 09:41 AM, Stefan Håkansson LK wrote:
> >>> Hi all,
> >>>
> >>> I've updated the WiKi page [1] based on what I heard at the teleconf
> >>> September 3rd. Feedback and comments are appreciated.
> >>>
> >>> Note that I'm not claiming this represents consensus, or that I
> >>> correctly understood what people meant at the call. I'm just trying
> >>> to move the discussion forward.
> >>>
> >>> Stefan
> >>>
> >>> [1] www.w3.org/2011/04/webrtc/wiki/Transport_Control
> >>
> >> --
> >> Surveillance is pervasive. Go Dark.
> >>
> >>
>

Received on Friday, 18 October 2013 21:14:41 UTC