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

Using tracks instead of streams

From: Martin Thomson <martin.thomson@gmail.com>
Date: Mon, 11 Nov 2013 22:44:50 -0800
Message-ID: <CABkgnnUYraxr0nMFGa9h=3qWvJaRvjKb9PohddP2rSX0qx5W8Q@mail.gmail.com>
To: "public-webrtc@w3.org" <public-webrtc@w3.org>
This isn't rocket science, though it requires a degree of API-inversion.

Yes, I know that I'm breaking the rules with respect to use of
"attribute sequence<Foo>".  The rules are stupid.

partial interface RTCPeerConnection {
  // the set of tracks we are sending
  attribute sequence<Doohickey> sendTracks;
  // the set of tracks we are (maybe) receiving
  attribute sequence<Doohickey> receiveTracks;

  // add a track to the set of sending tracks
  Doohickey addSendTrack(MediaStreamTrack track);

  // fired when a remote track manifests
  attribute EventHandler? onremotetrack;

partial interface MediaStreamTrack {
  // the set of streams - i.e., synchronization contexts
  // that this track belongs to
  attribute sequence<MediaStream> streams;

interface DooHickey {
  readonly attribute MediaStreamTrack track;
  // and some other stuff
  attribute PriorityLevel priority;
  attribute unsigned long maxBitrate;
  // ellipsis

All the stream-related mechanisms are removed from RTCPeerConnection.
Nothing changes about the way that MSID and appID and those mechanisms

The reason that MediaStreamTrack gets an accessor for the set of
streams that it belongs to is that if you are navigating this object
mesh starting from RTCPeerConnection, you wouldn't otherwise be able
to find the streams that exist.  Without that, worst case, the browser
wouldn't have a strong reference it could use to manage garbage

We are still talking about Doohickeys, so that interface has an ellipsis on it.
Received on Tuesday, 12 November 2013 06:45:21 UTC

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