commit | c2406e4eaf7703c6c64d21318186adda791e09fd | [log] [tgz] |
---|---|---|
author | JT Teh <jtteh@webrtc.org> | Mon Jul 16 20:37:52 2018 |
committer | Commit Bot <commit-bot@chromium.org> | Mon Jul 16 20:38:02 2018 |
tree | 8dbbebc7dc78f1ba4994b7885f814930248e2d51 | |
parent | 056d811b6a044cd7e02da1133a520bc2d489836f [diff] |
Revert "Move allocation and rtp conversion logic out of payload router." This reverts commit 1da4d79ba3275b3fa48cad3b2c0949e0d3b7afe7. Reason for revert: Need to revert https://webrtc-review.googlesource.com/c/src/+/88220 This causes a merge conflict. So need to revert this first. Original change's description: > Move allocation and rtp conversion logic out of payload router. > > Makes it easier to write tests, and allows for moving rtp module > ownership into the payload router in the future. > > The RtpPayloadParams class is split into declaration and definition and > moved into separate files. > > Bug: webrtc:9517 > Change-Id: I8700628edff19abcacfe8d3a20e4ba7476f712ad > Reviewed-on: https://webrtc-review.googlesource.com/88564 > Commit-Queue: Stefan Holmer <stefan@webrtc.org> > Reviewed-by: Sebastian Jansson <srte@webrtc.org> > Cr-Commit-Position: refs/heads/master@{#23983} TBR=sprang@webrtc.org,stefan@webrtc.org,srte@webrtc.org Change-Id: I342c4bf483d975c87c706fe7f76f44e2dc60fe4c No-Presubmit: true No-Tree-Checks: true No-Try: true Bug: webrtc:9517 Reviewed-on: https://webrtc-review.googlesource.com/88821 Reviewed-by: JT Teh <jtteh@webrtc.org> Commit-Queue: JT Teh <jtteh@webrtc.org> Cr-Commit-Position: refs/heads/master@{#23991}
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.