W3C home > Mailing lists > Public > public-webrtc-logs@w3.org > July 2017

Re: [webrtc-pc] Should the spec describe addStream/onaddstream as legacy API?

From: Iñaki Baz Castillo via GitHub <sysbot+gh@w3.org>
Date: Tue, 25 Jul 2017 09:58:11 +0000
To: public-webrtc-logs@w3.org
Message-ID: <issue_comment.created-317689724-1500976689-sysbot+gh@w3.org>
Answering the issue question "_Should the spec describe addStream/onaddstream as legacy API?_":

*NO*: It's proven to be a bad, wrong and problematic API (I won't repeat again all the rationale already given about it).

What we (and all the users) should do is complain against Chrome for keeping it for years while all its competitors have already moved to (at least) the track based API.

And no, `addStream()` and `addTrack()` cannot live together.

GitHub Notification of comment by ibc
Please view or discuss this issue at https://github.com/w3c/webrtc-pc/issues/1125#issuecomment-317689724 using your GitHub account
Received on Tuesday, 25 July 2017 09:58:13 UTC

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