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

> Communicating the custom ID from the hosting application (browser) to the hosted application (JS code) would require a new JS API. It's preferable to only use standards-complying APIs, isn't it?

Nothing that can be done via custom app and custom JavaScript should need a specific W3 standard. You have an specific use case, I may have N other different use cases (in which I also communicate different apps/processes). We cannot request a "standard" for all of them.

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

Received on Monday, 19 February 2018 17:33:51 UTC