W3C home > Mailing lists > Public > public-webrtc-logs@w3.org > February 2018

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

From: Elad Alon via GitHub <sysbot+gh@w3.org>
Date: Mon, 19 Feb 2018 16:22:30 +0000
To: public-webrtc-logs@w3.org
Message-ID: <issue_comment.created-366741122-1519057350-sysbot+gh@w3.org>
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 https://github.com/w3c/webrtc-pc/issues/1775#issuecomment-366741122 using your GitHub account
Received on Monday, 19 February 2018 16:23:03 UTC

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