Define remote playback proto buffer

media/media_options.gni

 # Copyright 2014 The Chromium Authors. All rights reserved.
 # Use of this source code is governed by a BSD-style license that can be
 # found in the LICENSE file.
 
 import("//build/config/chromecast_build.gni")
 import("//build/config/features.gni")
 import("//testing/libfuzzer/fuzzer_test.gni")
 
 declare_args() {
   # Allows distributions to link pulseaudio directly (DT_NEEDED) instead of
@@ skipping 105 matching lines @@
         "cdm",
         "renderer",
       ]
       mojo_media_host = "browser"
     } else {
       mojo_media_services = [ "video_decoder" ]
       mojo_media_host = "gpu"
     }
   }
 }
+
+declare_args() {
+  # flag to enable media remoting feature.

[xhwang, 2016/08/25 20:00:15]

Could you please provide more context about what "media remoting feature" is?

[erickung1, 2016/09/01 09:05:05]

Sure, the media remoting is the original project we discussed.
Instead of using mojo::renderer and mojo:cdm, we decide to create its own mojo
service, its own renderer and its own media keys implementation, to covert
message to RPC using proto buffer in the render process, and send the byte array
to browser process.

With such solution, we can eliminate security concern on parsing data in browser
process.

+  media_remoting = true
+}