commit | 81d4bf7af6df732ff7456dc144ef726146c18627 | [log] [tgz] |
---|---|---|
author | Artem Titov <titovartem@webrtc.org> | Thu Jan 24 12:01:59 2019 +0000 |
committer | Commit Bot <commit-bot@chromium.org> | Thu Jan 24 12:02:12 2019 +0000 |
tree | d352b048eabdc1be0a43afe9edbc962aac46b20b | |
parent | 1e27fec293b0a8e82a41636b73e5f1ad9247d39e [diff] |
Revert "Delete RtpUtility::Payload, and refactor RTPSender to not use it" This reverts commit 171df9326200d1e01bce530e2ff01ac5890e6cb7. Reason for revert: Breaks downstream project Original change's description: > Delete RtpUtility::Payload, and refactor RTPSender to not use it > > Replaced by a payload type --> video codec map in RTPSenderVideo, > where it is used to select the right packetizer. > > Bug: webrtc:6883 > Change-Id: I43a635d5135c5d519df860a2f4287a4478870b0f > Reviewed-on: https://webrtc-review.googlesource.com/c/119263 > Reviewed-by: Rasmus Brandt <brandtr@webrtc.org> > Reviewed-by: Danil Chapovalov <danilchap@webrtc.org> > Commit-Queue: Niels Moller <nisse@webrtc.org> > Cr-Commit-Position: refs/heads/master@{#26380} TBR=danilchap@webrtc.org,brandtr@webrtc.org,nisse@webrtc.org Change-Id: I76489c29541827aaba72515a76db54bdb7495e28 No-Presubmit: true No-Tree-Checks: true No-Try: true Bug: webrtc:6883 Reviewed-on: https://webrtc-review.googlesource.com/c/119640 Reviewed-by: Artem Titov <titovartem@webrtc.org> Commit-Queue: Artem Titov <titovartem@webrtc.org> Cr-Commit-Position: refs/heads/master@{#26385}
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.