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

Re: [webrtc-pc] does MSID still work? (was: example 13: getReceivers semantics)

From: jan-ivar via GitHub <sysbot+gh@w3.org>
Date: Thu, 11 May 2017 14:12:50 +0000
To: public-webrtc-logs@w3.org
Message-ID: <issue_comment.created-300801880-1494511968-sysbot+gh@w3.org>
@taylor-b In cases of accidental collisions, highly unexpected and undesirable I think. Were it done on purpose, I wouldn't expect implementations to pull off synchronization anyway, even if things came from the same place, like in my fiddle experiment. There are only bad choices here. I mean, this is why we moved to `transceiver.mid`, isn't it?

I think my preference would be to note this pitfall in the spec, and mark `stream.id` as legacy. Then, as to what should happen, probably what already happens. I'll test how Chrome handles it.

GitHub Notification of comment by jan-ivar
Please view or discuss this issue at https://github.com/w3c/webrtc-pc/issues/1128#issuecomment-300801880 using your GitHub account
Received on Thursday, 11 May 2017 14:12:57 UTC

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