292d658b20
Changed the channel unittest to use locking when reading/writing the result variable. To do this, I had to move the result into the thread object, which in turn required me to properly handle the lifetime of the thread object, since it cannot disappear while we want to read the result. It is still possible to have the result being written to a local variable, but it will only be updated as the thread object is destroyed. It is used to for the implementation of CallOnThreadAndWaitForDone. The old CallOnThread is gone and replaced by ScopedCallThread instead. BUG=webrtc:5524 Review URL: https://codereview.webrtc.org/1736763006 Cr-Commit-Position: refs/heads/master@{#12027}
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. This page is maintained by the Google Chrome team.
Development
See http://www.webrtc.org/native-code/development for instructions on how to get started developing with the native code.
More info
- Official web site: http://www.webrtc.org
- Master source code repo: https://chromium.googlesource.com/external/webrtc
- 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