| commit | bb9b6d1b324c267495139264fdeb000bb7bee582 | [log] [tgz] |
|---|---|---|
| author | Diep Bui <diepbp@webrtc.org> | Mon Oct 17 07:35:19 2022 |
| committer | WebRTC LUCI CQ <webrtc-scoped@luci-project-accounts.iam.gserviceaccount.com> | Mon Oct 17 09:24:57 2022 |
| tree | 64bd3a40ae3653f1590819f232276b8fc2ad2c37 | |
| parent | 8ac539c6d6ed79d14d65d2dad9523560447e1022 [diff] |
Revert "Probe when network is loss limited." This reverts commit aa71259b06b72ba0fc5a28c0ffa4891c69c09441. Reason for revert: This commit chain seems to cause problems in LossBasedBwe. Original change's description: > Probe when network is loss limited. > > Trigger probes next process intervals if the loss based current state is either increasing or decreasing. 0/ first probe at the loss based estimate. 1/ if increasing: allow further probing. 2/ if decreasing: not allow further probing. > > > Bug: webrtc:12707 > Change-Id: I4e99edcbe4e2c315e8498ffb7fb2e589cdb4e666 > Reviewed-on: https://webrtc-review.googlesource.com/c/src/+/279041 > Commit-Queue: Diep Bui <diepbp@webrtc.org> > Reviewed-by: Per Kjellander <perkj@webrtc.org> > Cr-Commit-Position: refs/heads/main@{#38395} Bug: webrtc:12707 Change-Id: I1fb61337148faf6faaa0056dc25f14536a19a462 Reviewed-on: https://webrtc-review.googlesource.com/c/src/+/279480 Reviewed-by: Per Kjellander <perkj@webrtc.org> Bot-Commit: rubber-stamper@appspot.gserviceaccount.com <rubber-stamper@appspot.gserviceaccount.com> Commit-Queue: Diep Bui <diepbp@webrtc.org> Cr-Commit-Position: refs/heads/main@{#38410}
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.
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.