commit e814a0dee015fe06b53673f6b021825130413b56
author deadbeef <deadbeef@webrtc.org> Sat Feb 25 18:15:09 2017 -0800
committer Commit bot <commit-bot@chromium.org> Sun Feb 26 02:15:09 2017 +0000
tree e3fbf11a2a2b9601e5dc776599796ab469ebed86
parent f15fb452efe5a7082dd49faceba1ff123985f258

Adding "adapter" ORTC objects on top of ChannelManager/BaseChannel/etc.

This CL adds the following interfaces:
* RtpTransportController
* RtpTransport
* RtpSender
* RtpReceiver

They're implemented on top of the "BaseChannel" object, which is normally used
in a PeerConnection, and roughly corresponds to an SDP "m=" section. As a result
of this, there are several limitations:

* You can only have one of each type of sender and receiver (audio/video) on top
  of the same transport controller.
* The sender/receiver with the same media type must use the same RTP transport.
* You can't change the transport after creating the sender or receiver.
* Some of the parameters aren't supported.

Later, these "adapter" objects will be gradually replaced by real objects that don't
have these limitations, as "BaseChannel", "MediaChannel" and related code is
restructured. In this CL, we essentially have:

ORTC adapter objects -> BaseChannel -> Media engine
PeerConnection -> BaseChannel -> Media engine

And later we hope to have simply:

PeerConnection -> "Real" ORTC objects -> Media engine

See the linked bug for more context.

BUG=webrtc:7013
TBR=stefan@webrtc.org

Review-Url: https://codereview.webrtc.org/2675173003
Cr-Commit-Position: refs/heads/master@{#16842}