Index: webrtc/call/rtp_transport_controller.h |
diff --git a/webrtc/call/rtp_transport_controller.h b/webrtc/call/rtp_transport_controller.h |
new file mode 100644 |
index 0000000000000000000000000000000000000000..ad68792185aa4af10e716f4bcc145b7f484e2b66 |
--- /dev/null |
+++ b/webrtc/call/rtp_transport_controller.h |
@@ -0,0 +1,56 @@ |
+/* |
+ * Copyright (c) 2017 The WebRTC project authors. All Rights Reserved. |
+ * |
+ * Use of this source code is governed by a BSD-style license |
+ * that can be found in the LICENSE file in the root of the source |
+ * tree. An additional intellectual property rights grant can be found |
+ * in the file PATENTS. All contributing project authors may |
+ * be found in the AUTHORS file in the root of the source tree. |
+ */ |
+ |
+#ifndef WEBRTC_CALL_RTP_TRANSPORT_CONTROLLER_H_ |
+#define WEBRTC_CALL_RTP_TRANSPORT_CONTROLLER_H_ |
+ |
+#include "webrtc/modules/congestion_controller/include/congestion_controller.h" |
+ |
+namespace webrtc { |
+ |
+class VieRemb; |
+class PacketRouter; |
+ |
+// An RtpTransportController should own everything related to the RTP |
+// transport to/from a remote endpoint. We should have separate |
+// interfaces for send and receive sice, even if they are implemented |
stefan-webrtc
2017/02/17 11:59:28
since
|
+// by the same class. This is on ongoing refactoring project. At some |
stefan-webrtc
2017/02/17 11:59:28
-on
|
+// point, this class should be promoted to a public api under |
+// webrtc/api/rtp/. |
+// |
+// For a start, this object is just a collection of the objects needed |
+// by the VideoSendStream constructor. The plan is to move ownership |
+// of all RTP-related objects here, and add methods to create per-ssrc |
+// objects which would then be passed to VideoSendStream. |
+// |
+// This should also have a reference to the underlying |
+// webrtc::Transport. Currently, webrtc::Transport is implemented by |
+// WebRtcVideoChannel2 and WebRtcVoiceMediaChannel, and owned by |
+// WebrtcSession. It's unclear why video and audio uses different |
+// transports, possibly because it is implemented by BaseChannel and |
+// there are other reasons for BaseChannel subclasses specific for |
+// video and audio. |
+// |
+// Extracting the logic of the webrtc::Transport from BaseChannel and |
+// subclasses into a separate class seems to be a prerequesite for |
+// moving the transport here. As an interim step, using this class for |
+// video only, we could consider passing the WebRtcVideoChannel2 |
+// transport here. |
+class RtpTransportControllerSendInterface { |
+ public: |
+ virtual ~RtpTransportControllerSendInterface() {} |
+ virtual VieRemb* remb() = 0; |
stefan-webrtc
2017/02/17 11:59:28
Do you think it would be possible to use PacketRou
|
+ virtual PacketRouter* packet_router() = 0; |
stefan-webrtc
2017/02/17 11:59:28
PacketRouter will not have to be exposed any longe
nisse-webrtc
2017/02/17 12:35:15
I don't think any of the current accessor methods
|
+ virtual CongestionController* congestion_controller() = 0; |
+}; |
+ |
+} // namespace webrtc |
+ |
+#endif // WEBRTC_CALL_RTP_TRANSPORT_CONTROLLER_H_ |