Move direct use of VideoCapturer::VideoAdapter to VideoSinkWants.

webrtc/media/base/videosourceinterface.h

 /*
  *  Copyright (c) 2016 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_MEDIA_BASE_VIDEOSOURCEINTERFACE_H_
 #define WEBRTC_MEDIA_BASE_VIDEOSOURCEINTERFACE_H_
 
 #include "webrtc/media/base/videosinkinterface.h"
 #include "webrtc/base/callback.h"
 
 namespace rtc {
 
 // VideoSinkWants is used for notifying the source of properties a video frame
 // should have when it is delivered to a certain sink.
 struct VideoSinkWants {
   bool operator==(const VideoSinkWants& rh) const {
     return rotation_applied == rh.rotation_applied;
   }
   bool operator!=(const VideoSinkWants& rh) const { return !operator==(rh); }
 
   // Tells the source whether the sink wants frames with rotation applied.
   // By default, the rotation is applied by the source.
   bool rotation_applied = true;
+
+  enum class Resolution {KEEP, UP, DOWN};
+  Resolution resolution =  Resolution::KEEP;

[nisse-webrtc, 2016/02/17 08:19:46]

I don't think it's a good idea to have actions here. Specifying a "want" should
be an idempotent operation, so that repeated AddOrUpdateSink with the same sink
and the same wants should be harmless.

To me, it would make sense to have max_width and max_height, or if for some
reason that's not appropriate, I could live with a scale factor.

Choice mainly depends on the desired action if the source changes resolution
spontaneously: Should we keep scaling with the same factor (then the "wants"
should be that scale factor), or should we  aim for giving the sink an unchanged
resolution (then max_width and max_height is a better fit)?

[perkj_webrtc, 2016/02/17 17:16:29]

After discussions- we don't want to change aspect ratio - so decided on setting
max_number_of_pixels.

 };
 
 template <typename VideoFrameT>
 class VideoSourceInterface {
  public:
   virtual void AddOrUpdateSink(VideoSinkInterface<VideoFrameT>* sink,
                                const VideoSinkWants& wants) = 0;
   // RemoveSink must guarantee that at the time the method returns,
   // there is no current and no future calls to VideoSinkInterface::OnFrame.
   virtual void RemoveSink(VideoSinkInterface<VideoFrameT>* sink) = 0;
 
  protected:
   virtual ~VideoSourceInterface() {}
 };
 
 }  // namespace rtc
 #endif  // WEBRTC_MEDIA_BASE_VIDEOSOURCEINTERFACE_H_