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

@fippo, I think the Firefox use case is simpler because they build so much inside a Javascript context.
Part of the issue here is that one of the interfaces elad is looking at has access to the PeerConnection object (so anything built into its IDL can be exposed to it), but NOT its Javascript context (so maps and decorations added by Javascript is NOT visible to it), while the other interface that has to talk about the same peerconnections has the opposite access: Full access to Javascript and no access to C++ internals.


-- 
GitHub Notification of comment by alvestrand
Please view or discuss this issue at https://github.com/w3c/webrtc-pc/issues/1775#issuecomment-366778851 using your GitHub account

Received on Monday, 19 February 2018 19:02:02 UTC