commit | 17790c3d3cc06b137ecb7f6d6624f42e8bf8c7ba | [log] [tgz] |
---|---|---|
author | Artem Titov <titovartem@webrtc.org> | Tue Aug 28 13:48:59 2018 |
committer | Commit Bot <commit-bot@chromium.org> | Tue Aug 28 13:49:08 2018 |
tree | 6953cea22bb3967fba24735008364a606f8765d6 | |
parent | 38bdf21569b2c00f5cf0a20fcd8ef906ae5198d8 [diff] |
Revert "Rename VideoQualityTestFixtureInterface::Params.pipe into config." This reverts commit 7f2eab0c7efef13fe41c6e9c8e155a67a8a673c4. Reason for revert: https://bugs.chromium.org/p/chromium/issues/detail?id=878373 Original change's description: > Rename VideoQualityTestFixtureInterface::Params.pipe into config. > > Also make it optional and use default value, if optional is not > specified. It is done also for next refactoring, that will introduce > ability to override network simulation layer. > > Bug: webrtc:9630 > Change-Id: I88cf1f9c70857f3299b5c3e9580a98570768e129 > Reviewed-on: https://webrtc-review.googlesource.com/96121 > Reviewed-by: Erik Språng <sprang@webrtc.org> > Reviewed-by: Patrik Höglund <phoglund@webrtc.org> > Commit-Queue: Artem Titov <titovartem@webrtc.org> > Cr-Commit-Position: refs/heads/master@{#24454} TBR=phoglund@webrtc.org,sprang@webrtc.org,titovartem@webrtc.org Change-Id: I7535422ef6a662defb0f9dee32d62133fa0c8b8f No-Presubmit: true No-Tree-Checks: true No-Try: true Bug: webrtc:9630 Reviewed-on: https://webrtc-review.googlesource.com/96541 Reviewed-by: Artem Titov <titovartem@webrtc.org> Commit-Queue: Artem Titov <titovartem@webrtc.org> Cr-Commit-Position: refs/heads/master@{#24467}
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.
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.