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

Re: [webrtc-pc] example 13: getReceivers semantics

From: Taylor Brandstetter via GitHub <sysbot+gh@w3.org>
Date: Mon, 17 Apr 2017 22:53:43 +0000
To: public-webrtc-logs@w3.org
Message-ID: <issue_comment.created-294618846-1492469622-sysbot+gh@w3.org>
After the refactor the track event would still be fired. But only for `pc1`, since only `pc1` is receiving media. Isn't that what we want? Here's the relevant step in "applying a remote description":

> If the direction of the media description is `sendrecv` or `sendonly`, and `transceiver.receiver.track` has not yet been fired in a `track` event, [process the remote track](https://www.w3.org/TR/webrtc/#process-remote-track) for the media description, given transceiver.

"Process the remote track" may be a bad name for the series of steps, but the steps will add the track to the indicated stream(s) and fire the `track` event.

GitHub Notification of comment by taylor-b
Please view or discuss this issue at https://github.com/w3c/webrtc-pc/issues/1128#issuecomment-294618846 using your GitHub account
Received on Monday, 17 April 2017 22:53:49 UTC

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