Use ChannelMojo between the remoting daemon and network processes.

remoting/host/host_main.cc

Index: remoting/host/host_main.cc
diff --git a/remoting/host/host_main.cc b/remoting/host/host_main.cc
index f2afe5f7dbad67625154d71c2369020cc97fefc5..d0ea983b7527eae007f54ed85070a5dc560b7ef5 100644
--- a/remoting/host/host_main.cc
+++ b/remoting/host/host_main.cc
@@ -19,6 +19,7 @@
 #include "base/strings/stringprintf.h"
 #include "base/strings/utf_string_conversions.h"
 #include "build/build_config.h"
+#include "mojo/edk/embedder/embedder.h"
 #include "remoting/base/breakpad.h"
 #include "remoting/host/host_exit_codes.h"
 #include "remoting/host/logging.h"
@@ -211,6 +212,8 @@ int HostMain(int argc, char** argv) {
 
   remoting::LoadResources("");
 
+  mojo::edk::Init();

[joedow, 2016/10/24 17:42:51]

I'm not sure how expensive this call is for the other platforms, but IPC/Mojo is
only used when we are in multi-process mode so we might want to scope it:
#if defined(REMOTING_MULTI_PROCESS)
    mojo::edk::Init();
#endif

[Sergey Ulanov, 2016/10/24 17:53:15]

+1
It's also likely to affect binary size, as we don't currently use mojo on other
platforms

[Sam McNally, 2016/10/24 22:54:04]

Done.

+
   // Invoke the entry point.
   int exit_code = main_routine();
   if (exit_code == kInvalidCommandLineExitCode) {