Experiment for the nack module.

webrtc/video/video_receive_stream.h

Index: webrtc/video/video_receive_stream.h
diff --git a/webrtc/video/video_receive_stream.h b/webrtc/video/video_receive_stream.h
index f1061dc1302de7bfa39bcf9ffab2b962e43c3098..3aca570f99e9d3a96d19a0abc2f56f547029cd44 100644
--- a/webrtc/video/video_receive_stream.h
+++ b/webrtc/video/video_receive_stream.h
@@ -40,7 +40,9 @@ namespace internal {
 class VideoReceiveStream : public webrtc::VideoReceiveStream,
                            public I420FrameCallback,
                            public VideoRenderCallback,
-                           public EncodedImageCallback {
+                           public EncodedImageCallback,
+                           public NackSender,
+                           public KeyFrameRequestSender {

[stefan-webrtc, 2016/03/10 14:20:40]

Is there a point in webrtc::RtpRtcp implementing NackSender if
VideoReceiveStream already does?

[philipel, 2016/03/10 16:39:28]

No, not really, fixed

  public:
   VideoReceiveStream(int num_cpu_cores,
                      CongestionController* congestion_controller,
@@ -79,6 +81,12 @@ class VideoReceiveStream : public webrtc::VideoReceiveStream,
 
   void SetSyncChannel(VoiceEngine* voice_engine, int audio_channel_id);
 
+  // NackSender
+  void SendNack(const std::vector<uint16_t>& sequence_numbers) override;
+
+  // KeyFrameRequestSender
+  void RequestKeyFrame() override;
+
  private:
   static bool DecodeThreadFunction(void* ptr);
   void Decode();