490d76c9b3
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. This is code stems partly from https://webrtc-review.googlesource.com/c/src/+/134208 but without the RtpPacketHistory changes which were landed in https://webrtc-review.googlesource.com/c/src/+/134307 Bug: webrtc:8975 Change-Id: Iea9d3d32bee5512473744e9ef3a18018567fc272 Reviewed-on: https://webrtc-review.googlesource.com/c/src/+/135160 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@{#27868}
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 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.
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: http://build.chromium.org/p/client.webrtc
- Coding style guide
- Code of conduct