Refactoring and rewriting the chromoting jni instance to be chromoting session.

remoting/client/chromoting_client_runtime.h

Index: remoting/client/chromoting_client_runtime.h
diff --git a/remoting/client/chromoting_client_runtime.h b/remoting/client/chromoting_client_runtime.h
index d3082760c6200e8934d36af9bc1ecd91cc4d0c1c..e406528011a27843d2a977439961200108b7840e 100644
--- a/remoting/client/chromoting_client_runtime.h
+++ b/remoting/client/chromoting_client_runtime.h
@@ -70,7 +70,7 @@ class ChromotingClientRuntime {
     return url_requester_;
   }
 
-  // Must call and use log_writter on the network thread.
+  // Must call and use log_writer on the network thread.
   ChromotingEventLogWriter* log_writer();
 
  private:
@@ -87,6 +87,12 @@ class ChromotingClientRuntime {
   // References to native threads.
   scoped_refptr<AutoThreadTaskRunner> ui_task_runner_;
 
+  // TODO(nicholss): Auththreads will be leaked because they depend on the main

[Lambros, 2017/03/24 00:07:14]

s/Auththreads/AutoThreads ?

[nicholss, 2017/03/29 20:32:35]

Done.

+  // thread. We should update this class to use regular threads like the client
+  // plugin does.
+  // Longer term we should migrate most of these to background tasks execpt the

[Lambros, 2017/03/24 00:07:14]

except

[nicholss, 2017/03/29 20:32:35]

Done.

+  // network thread to TaskSchedular, removing the need for threads.

[Lambros, 2017/03/24 00:07:14]

TaskScheduler

[nicholss, 2017/03/29 20:32:35]

Done. This was copied from a comment given to me via another code review, I did
not proof it enough I guess. :)

+
   scoped_refptr<AutoThreadTaskRunner> display_task_runner_;
   scoped_refptr<AutoThreadTaskRunner> network_task_runner_;
   scoped_refptr<AutoThreadTaskRunner> file_task_runner_;