W3C home > Mailing lists > Public > public-webrtc-logs@w3.org > February 2018

Re: [webrtc-pc] pc.addTrack/removeTrack are confusing and mostly redundant. Mark as legacy?

From: Philipp Hancke via GitHub <sysbot+gh@w3.org>
Date: Fri, 02 Feb 2018 09:17:20 +0000
To: public-webrtc-logs@w3.org
Message-ID: <issue_comment.created-362530492-1517563039-sysbot+gh@w3.org>
So we got rid of the legacy streams API without specifiyng them. Philosophically that is bad but nobody volunteered to write the spec. It is very clear for developers that addStream is the legacy API.

addTrack/removeTrack is confusing because it is supported both in the "track-based" API (shipped in Firefox and recently Chrome) and the transceiver model (in FF59). And they behave *very* different in both models which creates a lot of confusion.

I dislike addTransceiver because it is much easier to explain a web developer
* "you take your stream from getUserMedia and add the stream to the peerconnection"  or
* "you take your stream from getUserMedia and add all the tracks to the peerconnection"
than to explain what a transceiver is.

GitHub Notification of comment by fippo
Please view or discuss this issue at https://github.com/w3c/webrtc-pc/issues/1758#issuecomment-362530492 using your GitHub account
Received on Friday, 2 February 2018 09:17:32 UTC

This archive was generated by hypermail 2.4.0 : Saturday, 6 May 2023 21:19:43 UTC