I have a use case where peer connections are produced in one process (namely Chrome's renderer process), but I then need to refer to them on another process ("perform this and that on peer connection this and that"). The latter instruction should originate from the renderer process (where JS code lives). It seems to me that making up a single-use, Chrome-only way of attaching an identifier to the peer connection, so that I might refer to it later when talking about the PC to the other process, would be inadvisable. Therefore this suggested standardized identifier. -- GitHub Notification of comment by eladalon1983 Please view or discuss this issue at https://github.com/w3c/webrtc-pc/issues/1775#issuecomment-366748375 using your GitHub accountReceived on Monday, 19 February 2018 16:49:38 UTC
This archive was generated by hypermail 2.4.0 : Saturday, 6 May 2023 21:19:43 UTC