- From: stefan hakansson via GitHub <sysbot+gh@w3.org>
- Date: Thu, 18 Jan 2018 09:51:09 +0000
- To: public-webrtc-logs@w3.org
@jan-ivar >Why would you only expect the `track` event on the initial OA exchange (keeping in mind that in the transceiver model, the remote track often exists prior to that first event as well)? I guess I had the mental model that you get the `track` event when there is a new incoming track to consider. But never mind that, I guess you can design your code so that getting the event several times is no problem, e.g. * check if the track is already handled - no need to do anything * add it to a MediaStream used for rendering (or recording or whatever) - if the track is already a member this would be a no-op (from mediacapture-main: `If track is already in stream's track set, then abort these steps.`) But that actually brings me back to the [first post here](https://github.com/w3c/webrtc-pc/issues/1729#issue-287276834): if multiple track events for the same is already handled by the app, why would getting it from multiple SRD(offer) be an issue? -- GitHub Notification of comment by stefhak Please view or discuss this issue at https://github.com/w3c/webrtc-pc/issues/1729#issuecomment-358594451 using your GitHub account
Received on Thursday, 18 January 2018 09:51:19 UTC