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

[Bug 20819] no priority API

From: <bugzilla@jessica.w3.org>
Date: Fri, 21 Jun 2013 06:19:19 +0000
To: public-webrtc@w3.org
Message-ID: <bug-20819-4991-ou1mDzCQpH@http.www.w3.org/Bugs/Public/>
https://www.w3.org/Bugs/Public/show_bug.cgi?id=20819

--- Comment #3 from Stefan Hakansson LK <stefan.lk.hakansson@ericsson.com> ---
(In reply to comment #2)
> I'd like to +1 this bug. I think now would be a good time to get a good API
> proposals and get it into the spec.

I brought forward before, and am proposing again, that we - in a similar vein
to how a "RTCDTMFSender" sender is created off a PeerConnection but bound to a
MediaStreamTrack - allow for the creation of an object that allows setting of
priority and other transport related things per track using the established
Constraints model.

So we could add to PeerConnection something like:

     RTCTransportHandler createTransportHandler (MediaStreamTrack track);

The TransportHandler would use Constraints, e.g.:

interface RTCTransportHandler {
     readonly attribute MediaStreamTrack track;
     TrackTransportConstraints? constraints ();
     void applyConstraints (TrackTransportConstraints constraints);
     attribute EventHandler onoverconstrained;
};

Constraints could be:

* Priority
* bitrate (min, max)
* audio content (speech or general audio)
* video codec operation (VBR, CBR)

and so on (and of course we need to agree on an initial set).

-- 
You are receiving this mail because:
You are on the CC list for the bug.
You are the assignee for the bug.
Received on Friday, 21 June 2013 06:19:20 UTC

This archive was generated by hypermail 2.3.1 : Monday, 23 October 2017 15:19:33 UTC