2 Commits

Author	SHA1	Message	Date
deadbeef	e814a0dee0	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}	2017-02-26 02:15:09 +00:00
deadbeef	4b1bf6c2f0	Adding placeholder ortc_unittests target. ... This will allow the trybots to be updated to start running this new test executable, so that they can be used when landing this CL which will replace the dummy test with real tests: https://codereview.webrtc.org/2675173003/ BUG=webrtc:7013 TBR=tommi@webrtc.org Review-Url: https://codereview.webrtc.org/2707013005 Cr-Commit-Position: refs/heads/master@{#16784}	2017-02-23 07:45:38 +00:00