1c7ff0d001
If there is only little space left in a packet, and the remaining data for a partially sent message is much larger, it will not generate a small fragment for this message. This is to avoid fragmenting a message into too many packets, as that increases the risk of losing messages when partial reliability is enabled. And when a stream doesn't want to generate a too small fragment, the scheduler should _not_ switch streams. It should only switch streams when a message has been fully sent. Previously, it would switch stream when a stream doesn't want to produce a message, but as noted above, that could happen for other reasons. This required some refactoring, which also increased its robustness by now only doing explicit stream switching on fully produced messages. Bug: webrtc:12832 Change-Id: Icb213774fd0d26fba5640b00aac0407d393e4bfc Reviewed-on: https://webrtc-review.googlesource.com/c/src/+/220937 Commit-Queue: Victor Boivie <boivie@webrtc.org> Reviewed-by: Harald Alvestrand <hta@webrtc.org> Cr-Commit-Position: refs/heads/master@{#34197}
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