fbf0ac0ecd
RFC8831, section 6.7 states that closing a data channel MUST be signaled as resetting an outgoing stream, and that will ensure that all messages are either delivered or abandoned before the stream is reset. In the current implementation, dcSCTP has opted to abandoned any queued messages that haven't been partially sent. And this CL simply adds more documentation around this choice. It's subject to change and a client implementation shouldn't depend on any such behavior as the RFC allows the implementation to decide. Bug: None Change-Id: I60305fe396a6a3f494d823c71e092acfeb6075b7 Reviewed-on: https://webrtc-review.googlesource.com/c/src/+/257167 Reviewed-by: Harald Alvestrand <hta@webrtc.org> Commit-Queue: Victor Boivie <boivie@webrtc.org> Cr-Commit-Position: refs/heads/main@{#36395}
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