55dd72c54b
Also adding code in preparation of hiding the Module implementation in PacedSender. The implementation details of how the PacedSender+ProcessThread interaction works, has now been moved into PacedSender (and out of RtpTransportControllerSend). Instead of adding a "GetModuleImplementationForTesting" method to the PacedSender class (which would have been the lazy way out), I incorporated MockedProcessThread in the PacedSender tests. This means more boilerplate code but the Module functionality can be tested separately from the PacedSender and down the line I think it would be a good idea to start using a separate thread in the test, which is how the class under test is really used in production. Bug: none Change-Id: Iec1b7c97cb0b363b331143ca70545e6ebafe2cd4 Reviewed-on: https://webrtc-review.googlesource.com/c/src/+/149176 Commit-Queue: Tommi <tommi@webrtc.org> Reviewed-by: Erik Språng <sprang@webrtc.org> Cr-Commit-Position: refs/heads/master@{#29011}
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 http://www.webrtc.org/native-code/development 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