commit | f8c1ed564675889d4ba90d2c520d9109708a1ddd | [log] [tgz] |
---|---|---|
author | Erik Språng <sprang@webrtc.org> | Thu Apr 25 07:49:21 2019 |
committer | Commit Bot <commit-bot@chromium.org> | Thu Apr 25 07:49:31 2019 |
tree | 11ee6d5e7ac1a3ea87e813b8222583350ab246bc | |
parent | ce9281794f8853c4cfac36c4ea9174a1bf983496 [diff] |
Revert "Remove packets from RtpPacketHistory if acked via TransportFeedback" This reverts commit 3890e99b705065dbc60e6d16932d8584bd67200d. Reason for revert: Seems to be causing unexpected perf regressions. Original change's description: > Remove packets from RtpPacketHistory if acked via TransportFeedback > > If the receiver has indicated that a packet has been received, via a > TransportFeedback RTCP message, it is safe to remove it from the > RtpPacketHistory as we can be sure it won't be needed anymore. > This will reduce memory usage, reduce the risk of overflow in the > history at very high bitrates, and hopefully make payload based padding > a little more useful. > > Bug: webrtc:8975 > Change-Id: I703a353252943f63d7d6edda68f03bc482633fd6 > Reviewed-on: https://webrtc-review.googlesource.com/c/src/+/133028 > Commit-Queue: Erik Språng <sprang@webrtc.org> > Reviewed-by: Sebastian Jansson <srte@webrtc.org> > Reviewed-by: Danil Chapovalov <danilchap@webrtc.org> > Cr-Commit-Position: refs/heads/master@{#27745} TBR=danilchap@webrtc.org,sprang@webrtc.org,srte@webrtc.org Change-Id: I68ea6cf5c8988d4b625f14a1a9bc556c06a39368 No-Presubmit: true No-Tree-Checks: true No-Try: true Bug: webrtc:8975 Reviewed-on: https://webrtc-review.googlesource.com/c/src/+/134161 Reviewed-by: Erik Språng <sprang@webrtc.org> Commit-Queue: Erik Språng <sprang@webrtc.org> Cr-Commit-Position: refs/heads/master@{#27752}
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.