commit | de88b08b94b71fde9b43fdca38d39a95fe35889d | [log] [tgz] |
---|---|---|
author | Victor Boivie <boivie@webrtc.org> | Mon May 03 13:52:53 2021 |
committer | WebRTC LUCI CQ <webrtc-scoped@luci-project-accounts.iam.gserviceaccount.com> | Mon May 03 16:12:30 2021 |
tree | a1fe3f9ed5e67f617ab8f40fe965beea15c5803a | |
parent | 02e079ff809da021e841b9fc5b111bd3c17021e1 [diff] |
dcsctp: Add TaskQueue based timeout implementation This is about doing the best with what we have. As delayed tasks can't be cancelled, and dcSCTP timers will almost always be stopped or restarted, and will generally only expire on packet loss. This implementation will post a delayed task whenever a Timeout is started. Whenever it's stopped or restarted, it will keep the scheduled delay task running (there's no alternative), but it will also not start a new delayed task on subsequent starts/restarts. Instead, it will wait until the original delayed task has triggered, and will then - if the timer is still running, which it probably isn't - post a new delayed task with the remainder of the the duration. There is special handling for when a shorter duration is requested, as that can't re-use the scheduled task, but that shouldn't be very common. Bug: webrtc:12614 Change-Id: I7f3269cabf84f80dae3b8a528243414a93d50fc4 Reviewed-on: https://webrtc-review.googlesource.com/c/src/+/217223 Reviewed-by: Tommi <tommi@webrtc.org> Reviewed-by: Mirko Bonadei <mbonadei@webrtc.org> Commit-Queue: Victor Boivie <boivie@webrtc.org> Cr-Commit-Position: refs/heads/master@{#33904}
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.