Use ChannelMojo between the remoting daemon and network processes.

remoting/base/auto_thread_task_runner.h

Index: remoting/base/auto_thread_task_runner.h
diff --git a/remoting/base/auto_thread_task_runner.h b/remoting/base/auto_thread_task_runner.h
index e8efe97c82026ac3068d486e998b93f7bdd352bc..5e9ca6a31fccbf3b52142d3305dff5bf9835075e 100644
--- a/remoting/base/auto_thread_task_runner.h
+++ b/remoting/base/auto_thread_task_runner.h
@@ -34,6 +34,10 @@ class AutoThreadTaskRunner : public base::SingleThreadTaskRunner {
                                   base::TimeDelta delay) override;
   bool RunsTasksOnCurrentThread() const override;
 
+  const scoped_refptr<base::SingleThreadTaskRunner>& underlying_task_runner() {

[joedow, 2016/10/20 17:40:03]

What is the problem when passing an instance of this class directly to Mojo
(since it overrides SingleThreadTaskRunner)?  

I'd probably just call this member 'task_runner()'.  It feels odd to indicate in
the property name that encapsulation is being broken by stating 'underlying'.

[Sam McNally, 2016/10/20 22:40:22]

The mojo system holds onto its IO task runner forever so the IO thread never
shuts down and because the IO thread shutdown is set to run on the main thread,
it never stops and so the remoting host never shuts down.

+    return task_runner_;
+  }
+
  private:
   ~AutoThreadTaskRunner() override;