- From: Taylor Brandstetter via GitHub <sysbot+gh@w3.org>
- Date: Wed, 08 Feb 2017 05:33:16 +0000
- To: public-webrtc-logs@w3.org
@aboba That's what it seemed to me. The "dispatch a receiver" steps for creating a track were identical to those in "create a receiver". And the steps for "when a track is removed" are covered by the transceiver being stopped. This is the only time when a track *should* go to "ended", since that's a terminal state, and stopping a transceiver is the only terminal thing for its RtpReceiver. The differences I see are: * The previous text mentioned that "an event" is fired when the track state goes to "ended". It looks like this is missing from the "stop a transceiver" steps; I'll add it. * A task is queued to remove the receiver from the "set of receivers". This is no longer relevant here; there's a "set of transceivers" instead. -- GitHub Notification of comment by taylor-b Please view or discuss this issue at https://github.com/w3c/webrtc-pc/pull/1016#issuecomment-278233572 using your GitHub account
Received on Wednesday, 8 February 2017 05:33:22 UTC