Introduce a client minimum picture pool size

remoting/client/plugin/pepper_video_renderer_3d.cc

Index: remoting/client/plugin/pepper_video_renderer_3d.cc
diff --git a/remoting/client/plugin/pepper_video_renderer_3d.cc b/remoting/client/plugin/pepper_video_renderer_3d.cc
index 711c2104b702cf083f78a4b4b337286fb20eb91e..312bbe35ca1eb0532896a0657ea81a36abeb8d3a 100644
--- a/remoting/client/plugin/pepper_video_renderer_3d.cc
+++ b/remoting/client/plugin/pepper_video_renderer_3d.cc
@@ -172,6 +172,7 @@ void PepperVideoRenderer3D::OnSessionConfig(
   }
   int32_t result = video_decoder_.Initialize(
       graphics_, video_profile, PP_HARDWAREACCELERATION_WITHFALLBACK,
+      kMinimumPictureCount,

[Sergey Ulanov, 2015/08/11 23:10:20]

Actually looking at the implementation it appears that this call will fail in
older versions of browser that don't support the new version of the interface.
So maybe detect here if the new interface is supported and pass 0 otherwise?

[lpique, 2015/08/12 01:08:50]

Yikes. I didn't even think about this being a plugin when responding to your
last feedback.

I'm going to have to deal with the fact that the new version of the API is
Dev-channel only as well. Perhaps it is better to use zero for now, and leave a
TODO behind to change it to three once the API is promoted out of dev.

       callback_factory_.NewCallback(&PepperVideoRenderer3D::OnInitialized));
   CHECK_EQ(result, PP_OK_COMPLETIONPENDING)
       << "video_decoder_.Initialize() returned " << result;