Pepper API implementation for output protection.

chrome/browser/renderer_host/pepper/chrome_browser_pepper_host_factory.cc

Index: chrome/browser/renderer_host/pepper/chrome_browser_pepper_host_factory.cc
diff --git a/chrome/browser/renderer_host/pepper/chrome_browser_pepper_host_factory.cc b/chrome/browser/renderer_host/pepper/chrome_browser_pepper_host_factory.cc
index f7b48f74a00ae5f772c5915c256d4432d9c4ef16..227ef2f99c65ceee0fbfcac7853f4fc181e349a9 100644
--- a/chrome/browser/renderer_host/pepper/chrome_browser_pepper_host_factory.cc
+++ b/chrome/browser/renderer_host/pepper/chrome_browser_pepper_host_factory.cc
@@ -10,6 +10,7 @@
 #include "chrome/browser/renderer_host/pepper/pepper_flash_browser_host.h"
 #include "chrome/browser/renderer_host/pepper/pepper_flash_clipboard_message_filter.h"
 #include "chrome/browser/renderer_host/pepper/pepper_flash_drm_host.h"
+#include "chrome/browser/renderer_host/pepper/pepper_output_protection_host.h"
 #include "chrome/browser/renderer_host/pepper/pepper_talk_host.h"
 #include "content/public/browser/browser_ppapi_host.h"
 #include "ppapi/host/message_filter_host.h"
@@ -73,6 +74,12 @@ scoped_ptr<ResourceHost> ChromeBrowserPepperHostFactory::CreateResourceHost(
       case PpapiHostMsg_Talk_Create::ID:
         return scoped_ptr<ResourceHost>(new PepperTalkHost(
             host_, instance, params.pp_resource()));
+#if defined(OS_CHROMEOS)
+      case PpapiHostMsg_OutputProtection_Create::ID: {
+        return scoped_ptr<ResourceHost>(new PepperOutputProtectionHost(

[DaleCurtis, 2013/09/12 01:23:13]

While reviewing your code, I'm beginning to think that given the work both of
our APIs are doing on the UI thread, maybe we should be using a
MessageFilterHost w/ the UI thread instead of ResourceHost with hopping.

MessageFilterHost allows us to set OverrideTaskRunnerForMessage() to the UI
thread.  Which would mean we can get rid of the paired BlahBlah and
BlahBlahOnUIThread methods.  See PepperBrokerMessageFilter for an example of
this.

dmichael, WDYT?

[dmichael (off chromium), 2013/09/12 16:49:10]

Good point, if you don't have to do work on the IO thread before posting to the
UI thread, that's probably  a better approach.

[kcwu, 2013/09/12 18:22:08]

Done.
However, I still need to post task in dtor since the dtor is not
invoked in UI thread.

+            host_, instance, params.pp_resource()));
+      }
+#endif
     }
   }