b2d539be6b
The Data Tracker's purpose is to keep track of all received DATA chunks and to ACK/NACK that data, by generating SACK chunks reflecting its view of what has been received and what has been lost. It also contains logic for _when_ to send the SACKs, as that's different depending on e.g. packet loss. Generally, SACKs are sent every second packet on a connection with no packet loss, and can also be sent on a delayed timer. In case partial reliability is used, and the transmitter has decided that some data shouldn't be retransmitted, it will send a FORWARD-TSN chunk, which this class also handles, by "forgetting" about those chunks. Bug: webrtc:12614 Change-Id: Ifafb0c211f6a47872e81830165ab5fc43ee7f366 Reviewed-on: https://webrtc-review.googlesource.com/c/src/+/213664 Commit-Queue: Victor Boivie <boivie@webrtc.org> Reviewed-by: Tommi <tommi@webrtc.org> Cr-Commit-Position: refs/heads/master@{#33676}
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 here 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
- Reporting bugs