6b9c60b06d
The PacedSender currently has logic to temporarily release its internal lock while sending or asking for padding. This creates some tricky situations in the pacing controller where we need to consider if some thread can enter while we the process thread is actually processing, just temporarily busy sending. Since the pacing call stack is no longer cyclic, we can actually remove this lock-release now. Bug: webrtc:10809 Change-Id: Ic59c605252bed1f96a03406c908a30cd1012f995 Reviewed-on: https://webrtc-review.googlesource.com/c/src/+/173592 Reviewed-by: Sebastian Jansson <srte@webrtc.org> Commit-Queue: Erik Språng <sprang@webrtc.org> Cr-Commit-Position: refs/heads/master@{#31206}
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