| commit | 54dbc3be3fdbb77554d47a4bcede94f6cb8ad602 | [log] [tgz] |
|---|---|---|
| author | Artem Titov <titovartem@webrtc.org> | Thu Mar 11 09:00:15 2021 |
| committer | Commit Bot <commit-bot@chromium.org> | Thu Mar 11 09:01:01 2021 |
| tree | ad5274792a497fcdd94eccb54b5baa10b922e57f | |
| parent | 31357723267143f3e82ff5ce17df5512cd0e3335 [diff] |
Revert "[Battery]: Delay start of TaskQueuePacedSender." This reverts commit 89cb65ed663a9000b9f7c90a78039bd85731e9ae. Reason for revert: Breaks downstream project Original change's description: > [Battery]: Delay start of TaskQueuePacedSender. > > To avoid unnecessary repeating tasks, TaskQueuePacedSender is started > only upon RtpTransportControllerSend::EnsureStarted(). > > More specifically, the repeating task happens in > TaskQueuePacedSender::MaybeProcessPackets() every 500ms, using a self > task_queue_.PostDelayedTask(). > > Bug: chromium:1152887 > Change-Id: I72c96d2c4b491d5edb45a30b210b3797165cbf48 > Reviewed-on: https://webrtc-review.googlesource.com/c/src/+/208560 > Commit-Queue: Etienne Pierre-Doray <etiennep@chromium.org> > Reviewed-by: Henrik Boström <hbos@webrtc.org> > Reviewed-by: Erik Språng <sprang@webrtc.org> > Cr-Commit-Position: refs/heads/master@{#33421} Bug: chromium:1152887 Change-Id: I781d3bf614d5d0c03f292c0e478f24ede91624bb No-Presubmit: true No-Tree-Checks: true No-Try: true Reviewed-on: https://webrtc-review.googlesource.com/c/src/+/211345 Reviewed-by: Artem Titov <titovartem@webrtc.org> Commit-Queue: Artem Titov <titovartem@webrtc.org> Cr-Commit-Position: refs/heads/master@{#33430}
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.