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

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

From: Philipp Hancke via GitHub <sysbot+gh@w3.org>
Date: Thu, 15 Jun 2017 12:33:02 +0000
To: public-webrtc-logs@w3.org
Message-ID: <issue_comment.created-308716579-1497529980-sysbot+gh@w3.org>
@stefhak the Chrome behaviour is consistent with the addStream-model on the other side. If a track gets added to a remote stream, onaddtrack is called on the stream without things going through the peerconnection. Now in the addTrack-model it makes no sense. @taylor-b actually [mentioned this](https://github.com/w3c/webrtc-pc/issues/1125#issuecomment-296788876) back in April.

The first part of my [second comment](https://github.com/w3c/webrtc-pc/issues/1125#issuecomment-308708976) was a comment on @jan-ivar's "[wildy misleading](https://github.com/w3c/webrtc-pc/issues/1125#issuecomment-294265922)".
The second part was about unexpected combinations we need to take into account when specifying addStream ontop of addTrack.

-- 
GitHub Notification of comment by fippo
Please view or discuss this issue at https://github.com/w3c/webrtc-pc/issues/1125#issuecomment-308716579 using your GitHub account
Received on Thursday, 15 June 2017 12:33:08 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 4 June 2019 15:32:44 UTC