- From: Elad Alon via GitHub <sysbot+gh@w3.org>
- Date: Mon, 19 Feb 2018 17:25:03 +0000
- To: public-webrtc-logs@w3.org
I think I am referring to the intersection of C++ and JS code. Please pardon my unfamiliarity with the established terminology, making me invent my own. Let me call an application such as a browser the "hosting application", and a JS-based application the "hosted application". Different hosting applications might define their own new functionality. It may be specific to that hosting application. To give some made-up examples, it could be that one browser wants to allow an API that would rate-limit a given peer connection, and another browser wants to add an API that limits the time that a peer connection may remain open. Normally, this would be achievable with just giving a reference to the RTCPeerConnection object, so no problem. But this assumes a specific structure of the hosting application. Namely, it assumes that the application is single-process, and that the API called for "please rate limit X" is the same process where X lives. Normally, this assumption is true. But not always. When it doesn't hold true, the hosting application would need to invent its own naming scheme that would allow one to say "please do Z on peer connection X." That is possible. But it would be easier if there were a standardized way of saying "peer connection X", which would work *even* when a reference to the actual RTCPeerConnection is out of the question. -- GitHub Notification of comment by eladalon1983 Please view or discuss this issue at https://github.com/w3c/webrtc-pc/issues/1775#issuecomment-366757697 using your GitHub account
Received on Monday, 19 February 2018 17:25:05 UTC