| commit | b210eeb81245987e52e51994513a0a0f888f16b8 | [log] [tgz] |
|---|---|---|
| author | Erik Språng <sprang@webrtc.org> | Tue Nov 05 10:21:48 2019 |
| committer | Commit Bot <commit-bot@chromium.org> | Tue Nov 05 11:02:22 2019 |
| tree | fc22f9f8b8fab70a14181be265c03b6326740b9b | |
| parent | 19834589816862778546b41154e9a7d4c0c30ca2 [diff] |
Reland "Refactors BitrateProber with unit types and absolute probe time." This is a reland of 739a5b3692880cb6b41ae620fb9e755c39b044b1 Patchset 1 is the original CL, patchset 3 includes a fix Original change's description: > Refactors BitrateProber with unit types and absolute probe time. > > Using unit types improves readability and some conversion in PacedSender > can be removed. > > TimeUntilNextProbe() is replaced by NextProbeTime(), so returning an > absolute time rather than a delta. This fits better with the upcoming > TaskQueue based pacer, and is also what is already stored internally > in BitrateProber. > > Bug: webrtc:10809 > Change-Id: I5a4e289d2b53e99d3c0a2f4b36a966dba759d5cf > Reviewed-on: https://webrtc-review.googlesource.com/c/src/+/158743 > Commit-Queue: Erik Språng <sprang@webrtc.org> > Reviewed-by: Sebastian Jansson <srte@webrtc.org> > Cr-Commit-Position: refs/heads/master@{#29670} Bug: webrtc:10809 Change-Id: I033193c78474fdd82c109fdab0a8f09a05f7b30e Reviewed-on: https://webrtc-review.googlesource.com/c/src/+/158841 Commit-Queue: Erik Språng <sprang@webrtc.org> Reviewed-by: Sebastian Jansson <srte@webrtc.org> Cr-Commit-Position: refs/heads/master@{#29688}
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 http://www.webrtc.org/native-code/development for instructions on how to get started developing with the native code.
Authoritative list of directories that contain the native API header files.