- From: Mark Roberts via GitHub <sysbot+gh@w3.org>
- Date: Wed, 12 Jul 2017 19:07:41 +0000
- To: public-webrtc-logs@w3.org
@jan-ivar Thanks for the article and blog. If I had to update our application to handle this behavior today, I think I'd actually opt for the MediaStream ID approach you shared. It is nice because the MediaStream ID can be known in advance. So my application can say, "Hey, expect to receive MediaStream X" in advance of sending any offer, sending any answer, or even custructing an RTCPeerConnection. With MID, I cannot know the RTCRtpTransceiver's `mid` until applying a description, so I don't know how I could signal what to expect ahead of time. -- GitHub Notification of comment by markandrus Please view or discuss this issue at https://github.com/w3c/webrtc-pc/issues/1128#issuecomment-314867256 using your GitHub account
Received on Wednesday, 12 July 2017 19:07:51 UTC