- From: Robin Schriebman via GitHub <sysbot+gh@w3.org>
- Date: Tue, 06 Mar 2018 21:47:32 +0000
- To: public-webrtc-logs@w3.org
So I have another use case for this. On the application side we report a decent amount of telemetry tied to our own concepts of session identifiers. On the webrtc side (and I presume any webrtc implementation), they also have a decent amount of internal telemetry that the js doesn't (and likely shouldn't know). However, after the fact, we get reports with issues that are tied to our identifiers. It would be really nice to have a short succinct way of reporting this in a way that is understandable to both sides. We've actually gotten around this by adding a "setMetadata" call to our private api that allows us to pass our session identifier, but this way would make a lot more sense. -- GitHub Notification of comment by icydragons Please view or discuss this issue at https://github.com/w3c/webrtc-pc/issues/1775#issuecomment-370940374 using your GitHub account
Received on Tuesday, 6 March 2018 21:47:34 UTC