f4fa166cc5
It's to be used for clients to record metrics and to e.g. attribute metrics to which SCTP implementation the peer was using. This is not explicitly signaled, so heuristics are used. These are not guaranteed to come to the correct conclusion, and the data is not always available. Note: The behavior of dcSCTP will not change depending on the assumed implementation - only by explicitly signaled capabilities. Bug: webrtc:13216 Change-Id: I2f58054d17d53d947ed5845df7a08f974d42f918 Reviewed-on: https://webrtc-review.googlesource.com/c/src/+/233100 Reviewed-by: Harald Alvestrand <hta@webrtc.org> Commit-Queue: Victor Boivie <boivie@webrtc.org> Cr-Commit-Position: refs/heads/main@{#35103}
WebRTC is a free, open software project that provides browsers and mobile applications with Real-Time Communications (RTC) capabilities via simple APIs. The WebRTC components have been optimized to best serve this purpose.
Our mission: To enable rich, high-quality RTC applications to be developed for the browser, mobile platforms, and IoT devices, and allow them all to communicate via a common set of protocols.
The WebRTC initiative is a project supported by Google, Mozilla and Opera, amongst others.
Development
See here for instructions on how to get started developing with the native code.
Authoritative list of directories that contain the native API header files.
More info
- Official web site: http://www.webrtc.org
- Master source code repo: https://webrtc.googlesource.com/src
- Samples and reference apps: https://github.com/webrtc
- Mailing list: http://groups.google.com/group/discuss-webrtc
- Continuous build: https://ci.chromium.org/p/webrtc/g/ci/console
- Coding style guide
- Code of conduct
- Reporting bugs
- Documentation