Intent to implement: RTCPeerConnection.id (with origin trial)

[elad...@chromium.org]

Contact emails

elad...@chromium.org

Explainer

Explainer doc

Design doc/Spec

See the explainer doc above.

Summary

An origin trial-gated RTCPeerConnection.id would allow us to have an identity marker on a peer connection, by which we would be able to indicate specific peer connections when we invoke API calls on a different process than the renderer process.

Motivation

This attributes makes it possible to identify a peer connection in contexts separate from JavaScript such as other processes or an external logging facility.

Risks

Interoperability and Compatibility

There is no risk to breaking existing applications, as this is new, and is not yet used by any applications.

Interoperability with other browsers is a concern. To address this, the new attribute will be part of an origin trial. If the trial is successful and the attribute is standardized, we expect that other browsers will implement it.

Ergonomics

No performance issues are expected to be introduced by this feature.

Activation

This will initially be gated by an origin trial.

Will this feature be supported on all six Blink platforms (Windows, Mac, Linux, Chrome OS, Android, and Android WebView)

Yes.

Link to entry on the feature dashboard

Link

Requesting approval to ship?

No.

[Philip Jägenstedt]

No LGTMs required to implement, but for origin trials please send an Intent to Experiment, template here:

https://docs.google.com/document/d/1vlTlsQKThwaX0-lj_iZbVTzyqY7LioqERU8DK3u3XjI/edit#bookmark=id.pygli2e122ic

Having a handle for some object in the main thread for use on other processes is quite similar to what WebDriver does for elements:

https://w3c.github.io/webdriver/webdriver-spec.html#dfn-web-element-reference

This identifier isn't web-exposed though and a script can't see it. For your use case, would that be a problem?

--
You received this message because you are subscribed to the Google Groups "blink-dev" group.
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/3f4a5148-d49b-4593-95ed-45ce735e389a%40chromium.org.

[elad...@chromium.org]

• The Intent to Experiment is here.
  
• The motivation for RTCPeerConnection.id is a case where I need the identifier to be exposed to a JS application.