#WebRTC allows real-time audio/video connections in browsers, either in #P2P mode or mediated by server components.
This first Candidate Recommendation of WebRTC Stats define a set of metrics to monitor and debug these connections #timetoimplement
This tweet is unavailable
1
2
3
The API is developed in its own github repo under the editorship of @vr000m and @alvestrand
github.com/w3c/webrtc-stats/
Jul 3, 2018 · 1:29 PM UTC
1
1
.@w3c Working Groups need to demonstrate during #CandidateRecommendation that their specifications have interoperable implementations.
Usually, for browser techs, they do this by developing and running tests in Web Platform Tests github.com/web-platform-test…
All the features that are defined in @w3c specifications to be shipped in browsers are accompanied by a test suite, to help assess how well and how broadly they are implemented by actual browsers.
1
1
For WebRTC Stats, evaluating and verifying interoperability for its defined metrics is hard: they reflect ever changing network and system conditions, e.g. round-trip time between 2 remote browsers w3.org/TR/webrtc-stats/#dom-…
1
Because of this and other #WebRTC specificities, an open source #WebRTC-specific test framework, KITE, has been developed to complement the usual Web Platform Tests github.com/webrtc/KITE
1
3
1
2
And that level of control will also enable to test to a higher degree of confidence the level of interoperability for #WebRTC Stats metrics.
@callstatsio (a great consumer of these metrics) have already started exploring this webrtc-stats.callstats.io/ve…
1
4
4
WebRTC stats, its current status and its possible future evolutions were discussed at the recent #WebRTC Working Group meeting (see slides 75-87 in w3.org/2011/04/webrtc/wiki/i…)
LIVE REPORT! The #WebRTC #WorkingGroup is meeting in #Stockholm 🇸🇪 today and tomorrow. A major focus is to look at the future of #WebRTC: which use cases it should cover, which new #APIs it should expose, and new ways of interacting with it (e.g. in workers)
