Re: [webrtc-pc] RTCPeerConnection lacks identity marker beyond current process

@fippo, the identifier exposed by the hosting application need not be the internal ID that the application regularly uses. If we give the Chrome implementation as an example, you might see that an int is used for identifying peer connections internally, whereas the ID I've proposed to be used externally would be a randomly selected hexadecimal string.

About the general reservations to adding this attribute, I am waiting for some of my more experienced colleagues to come forward with other justifications for this proposal. Thank you all for your time and attention!

GitHub Notification of comment by eladalon1983
Please view or discuss this issue at using your GitHub account

Received on Monday, 19 February 2018 18:43:53 UTC