c1ad1ff178
Instead of doing a separate Invoke for each channel, this CL first gathers a list of operations to be performed on the signaling thread, then does a single Invoke on the worker thread (and nested Invoke on the network thread) to update all channels at once. This includes the methods: * Enable * SetLocalContent/SetRemoteContent * RegisterRtpDemuxerSink * UpdateRtpHeaderExtensionMap Also, removed the need for a network thread Invoke in IsReadyToSendMedia_w by moving ownership of was_ever_writable_ to the worker thread. Bug: webrtc:12266 Change-Id: I31e61fe0758aeb053b09db84f234deb58dfb3d05 Reviewed-on: https://webrtc-review.googlesource.com/c/src/+/194181 Commit-Queue: Taylor <deadbeef@webrtc.org> Reviewed-by: Harald Alvestrand <hta@webrtc.org> Cr-Commit-Position: refs/heads/master@{#32817}
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