commit | 4a93da315b70b2600a7ff1b38d7431444377052d | [log] [tgz] |
---|---|---|
author | Victor Boivie <boivie@webrtc.org> | Fri May 27 12:30:24 2022 |
committer | WebRTC LUCI CQ <webrtc-scoped@luci-project-accounts.iam.gserviceaccount.com> | Tue Jul 05 15:37:53 2022 |
tree | 35a0f9455e255e2bd1049318ddcbbd3b17549da0 | |
parent | 72b12d42a6649d4321fd266e19ac8ae1a53c8978 [diff] |
dcsctp: Report acked/abandoned messages when acked For all messages where the last fragment was _not_ put on the wire, the send queue is responsible for generating lifecycle events, but once all fragments have been put on the wire, it's the retransmission queue that is responsible. It does that by marking the final fragment of a message with the lifecycle identifier, and once that message has been fully acked by the cumulative ack TSN, it's clear that the peer has fully received all fragments of the message, as the last fragment was acked. For abandoned messages - where FORWARD-TSNs are sent, those will be replied to by a SACK as well, and then we report abandoned messages separately, to later trigger `OnLifecycleMessageExpired`. This CL adds support in OutstandingData, which doesn't generate the callbacks itself, but just reports them in the AckInfo. Bug: webrtc:5696 Change-Id: I64092f13bcfda685443b7df9967b04d54aedd36a Reviewed-on: https://webrtc-review.googlesource.com/c/src/+/264124 Reviewed-by: Harald Alvestrand <hta@webrtc.org> Commit-Queue: Victor Boivie <boivie@webrtc.org> Cr-Commit-Position: refs/heads/main@{#37448}
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 here for instructions on how to get started developing with the native code.
Authoritative list of directories that contain the native API header files.