| commit | a601f5c86310c078c21161947f526f2d1e65c9cc | [log] [tgz] |
|---|---|---|
| author | deadbeef <deadbeef@webrtc.org> | Mon Jun 06 14:27:39 2016 -0700 |
| committer | Commit bot <commit-bot@chromium.org> | Mon Jun 06 21:27:43 2016 +0000 |
| tree | b48e94f9a1dc7997e04c4fc6cef6a049f5d269e7 | |
| parent | aff499c9bf7e35cb0f5faf9a016ec97fb94c9e1c [diff] |
Separating internal and external methods of RtpSender/RtpReceiver. This moves the implementation specific methods to separate classes (RtpSenderInternal/RtpReceiverInternal) so that the interface classes represent the interface that external applications can rely on. The reason this wasn't done earlier was that PeerConnection needed to store proxy pointers, but also needed to access implementation- specific methods on the underlying objects. This is now possible by using "RtpSenderProxyWithInternal<RtpSenderInternal>", which is a proxy that implements RtpSenderInterface but also provides direct access to an RtpSenderInternal. Review-Url: https://codereview.webrtc.org/2023373002 Cr-Commit-Position: refs/heads/master@{#13056}
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.