b831eb816e
This makes it easier to remove use of sigslot for SignalEvent since the tests were written in a way that could set more than one event handlers to the same callback method, which places unnecessary requirements on the definition of the callback object. I.e. the sigslot can't be replaced with a simple (single) std::function - which would be consistent with how the event callback is used elsewhere in the code. Bug: webrtc:11943 Change-Id: I7e596295b1b534d4d49334449b1e01535eedf06d Reviewed-on: https://webrtc-review.googlesource.com/c/src/+/344723 Reviewed-by: Harald Alvestrand <hta@webrtc.org> Commit-Queue: Tomas Gunnarsson <tommi@webrtc.org> Cr-Commit-Position: refs/heads/main@{#42072}
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: https://ci.chromium.org/p/webrtc/g/ci/console
- Coding style guide
- Code of conduct
- Reporting bugs
- Documentation