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

Philipp, my intention was that a browser where the peer connection lives would normally follow the spec to the letter and only provide uppercase hexadecimal strings as IDs, but if ever given an ID from a JS application, would transform lowercase->uppercase before looking up the associated peer connection (*). I do not think the SDP is concerned, but maybe I am missing something?

* If this attribute is added to the API, one could have later APIs depend on this identifier.

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

Received on Monday, 19 February 2018 16:23:03 UTC