commit | c709412c76d8c6ee311ca2a96bdebdd9f8638f98 | [log] [tgz] |
---|---|---|
author | Sebastian Jansson <srte@webrtc.org> | Mon Jan 27 15:09:35 2020 |
committer | Commit Bot <commit-bot@chromium.org> | Mon Jan 27 15:09:49 2020 |
tree | 850ab630749663fa14483e6fbeeab11e560868d1 | |
parent | 8c79c6e1af354c526497082c79ccbe12af03a33e [diff] |
Revert "Only include overhead if using send side bandwidth estimation." This reverts commit 8c79c6e1af354c526497082c79ccbe12af03a33e. Reason for revert: Introduced a Bug that can happen if the include overhead state changes between pushing and poping a packet from the pacer packet queue. Original change's description: > Only include overhead if using send side bandwidth estimation. > > Bug: webrtc:11298 > Change-Id: Ia2daf690461b55d394c1b964d6a7977a98be8be2 > Reviewed-on: https://webrtc-review.googlesource.com/c/src/+/166820 > Reviewed-by: Oskar Sundbom <ossu@webrtc.org> > Reviewed-by: Sam Zackrisson <saza@webrtc.org> > Reviewed-by: Ali Tofigh <alito@webrtc.org> > Reviewed-by: Erik Språng <sprang@webrtc.org> > Commit-Queue: Sebastian Jansson <srte@webrtc.org> > Cr-Commit-Position: refs/heads/master@{#30382} TBR=saza@webrtc.org,ossu@webrtc.org,sprang@webrtc.org,srte@webrtc.org,alito@webrtc.org Change-Id: I0cacbc26408b7bec5bc3855a628e62407c081117 No-Presubmit: true No-Tree-Checks: true No-Try: true Bug: webrtc:11298 Reviewed-on: https://webrtc-review.googlesource.com/c/src/+/167523 Reviewed-by: Sebastian Jansson <srte@webrtc.org> Commit-Queue: Sebastian Jansson <srte@webrtc.org> Cr-Commit-Position: refs/heads/master@{#30383}
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.