- From: stefan hakansson via GitHub <sysbot+gh@w3.org>
- Date: Sat, 31 Dec 2016 07:21:59 +0000
- To: public-webrtc-logs@w3.org
@mparis re-reading the spec it seems pretty clear to me what should happen also at the receiver side. Say that the sender side app does something like ``` const trxA = pc.addTransceiver(trackX); const trxB = pc.addTransceiver(trackX); const trxC = pc.addTransceiver(trackX); ``` followed by createOffer, setLocal, send offer to remote side, which in turn does setRemote, then what happens is that three ```track``` events are fired by the remote pc, and the track in each of those events have the same id (i.e. the id of trackX). However, the remote and local app can still coordinate which is which by looking up the transceiver (which is included in the ```track``` event) and then correlate the ```mid```'s with those of ```trxA```, ```trxB``` and ```trxC```. -- GitHub Notification of comment by stefhak Please view or discuss this issue at https://github.com/w3c/webrtc-pc/issues/954#issuecomment-269853685 using your GitHub account
Received on Saturday, 31 December 2016 07:22:05 UTC