e0b45c268e
To allow the transport to be able to know which ranges of stream identifiers it can use, the negotiated incoming/inbound and outgoing/outbound stream counts will be exposed. They are added to Metrics, and guaranteed to be available from within the OnConnected callback. In this CL, dcSCTP will not validate that the client is sending on a stream that is within the negotiated bounds. That will be done as a follow-up CL. Bug: webrtc:14277 Change-Id: Ic764e5f93f53d55633ee547df86246022f4097cf Reviewed-on: https://webrtc-review.googlesource.com/c/src/+/272321 Reviewed-by: Harald Alvestrand <hta@webrtc.org> Commit-Queue: Victor Boivie <boivie@webrtc.org> Cr-Commit-Position: refs/heads/main@{#37876}
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