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

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

From: Iñaki Baz Castillo via GitHub <sysbot+gh@w3.org>
Date: Mon, 19 Feb 2018 17:33:49 +0000
To: public-webrtc-logs@w3.org
Message-ID: <issue_comment.created-366759991-1519061629-sysbot+gh@w3.org>
> 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 https://github.com/w3c/webrtc-pc/issues/1775#issuecomment-366759991 using your GitHub account
Received on Monday, 19 February 2018 17:33:51 UTC

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