| commit | 3cf8ece95400d1ffe2160eab8238c83f044d4b8c | [log] [tgz] |
|---|---|---|
| author | magjed <magjed@webrtc.org> | Thu Nov 10 11:36:53 2016 |
| committer | Commit bot <commit-bot@chromium.org> | Thu Nov 10 11:36:57 2016 |
| tree | 0b8a37d255ad49efa583a9a1ff592284702474fc | |
| parent | 792738640234d81c916ac4458ac72286cb2548a4 [diff] |
Revert of Stop caching supported codecs in WebRtcVideoEngine2 (patchset #1 id:1 of https://codereview.webrtc.org/2492473002/ ) Reason for revert: This CL probably broke Chromium FYI. Original issue's description: > Stop caching supported codecs in WebRtcVideoEngine2 > > We currently cache the result of GetSupportedCodecs in a member variable > |video_codecs_| in WebRtcVideoEngine2. This means we need to keep > |video_codecs_| and the result of GetSupportedCodecs in sync, which is > error prone. It's simpler to just call GetSupportedCodecs when we need > it, and we actually end up making fewer calls, so it's faster as well. > This CL also returns all std::vectors by-value instead of by-ref. Move > semantic together with in-place filtering of codecs actually end up with > fewer copies, and it's also simpler to not return references. > > BUG=webrtc:6337 > > Committed: https://crrev.com/9f71ec5a3e3175751f4475b126cfda89767363f2 > Cr-Commit-Position: refs/heads/master@{#15007} TBR=tommi@webrtc.org # Skipping CQ checks because original CL landed less than 1 days ago. NOPRESUBMIT=true NOTREECHECKS=true NOTRY=true BUG=webrtc:6337 Review-Url: https://codereview.webrtc.org/2489173004 Cr-Commit-Position: refs/heads/master@{#15014}
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.
See http://www.webrtc.org/native-code/development for instructions on how to get started developing with the native code.