Chromium Code Reviews
chromiumcodereview-hr@appspot.gserviceaccount.com (chromiumcodereview-hr) | Please choose your nickname with Settings | Help | Chromium Project | Gerrit Changes | Sign out
(176)

Unified Diff: remoting/client/chromoting_client_runtime.cc

Issue 1764503002: Adding container class for chromoting client runtimes. (Closed) Base URL: https://chromium.googlesource.com/chromium/src.git@master
Patch Set: Android and iOS both use MessageLoopForUI directly now. Created 4 years, 9 months ago
Use n/p to move between diff chunks; N/P to move between comments. Draft comments are only viewable by you.
Jump to:
View side-by-side diff with in-line comments
Download patch
Index: remoting/client/chromoting_client_runtime.cc
diff --git a/remoting/client/chromoting_client_runtime.cc b/remoting/client/chromoting_client_runtime.cc
new file mode 100644
index 0000000000000000000000000000000000000000..0bd62d17fad86e546a5396613b9e577b210bb665
--- /dev/null
+++ b/remoting/client/chromoting_client_runtime.cc
@@ -0,0 +1,56 @@
+// Copyright 2016 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.
+
+#include "remoting/client/chromoting_client_runtime.h"
+
+#include "base/bind.h"
+#include "base/logging.h"
+#include "base/memory/singleton.h"
+#include "remoting/base/url_request_context_getter.h"
+
+namespace remoting {
+
+ChromotingClientRuntime::ChromotingClientRuntime() {
+ if (!base::MessageLoop::current()) {
+ VLOG(1) << "Starting main message loop";
+ ui_loop_.reset(new base::MessageLoopForUI());
+#if defined(OS_IOS)
+ // On iOS we created a new message loop and now attach it.
+ base::MessageLoopForUI::current()->Attach();
+#elif defined(OS_ANDROID)
+ // On Android, the UI thread is managed by Java, so we need to attach and
+ // start a special type of message loop to allow Chromium code to run tasks.
+ ui_loop_->Start();
+#else
+ NOTREACHED();
+#endif
+ } else {
+ VLOG(1) << "Using existing main message loop";
+ ui_loop_.reset(base::MessageLoopForUI::current());
+ }
+
+ // |ui_loop_| runs on the main thread, so |ui_task_runner_| will run on the
+ // main thread. We can not kill the main thread when the message loop becomes
+ // idle so the callback function does nothing (as opposed to the typical
+ // base::MessageLoop::QuitClosure())
+ ui_task_runner_ = new AutoThreadTaskRunner(ui_loop_->task_runner(),
+ base::Bind(&base::DoNothing));
+
+ display_task_runner_ = AutoThread::Create("native_disp", ui_task_runner_);
+ network_task_runner_ = AutoThread::CreateWithType(
+ "native_net", ui_task_runner_, base::MessageLoop::TYPE_IO);
+ file_task_runner_ = AutoThread::CreateWithType("native_file", ui_task_runner_,
+ base::MessageLoop::TYPE_IO);
+ url_requester_ =
+ new URLRequestContextGetter(network_task_runner_, file_task_runner_);
+}
+
+// static
+ChromotingClientRuntime* ChromotingClientRuntime::GetInstance() {
+ return base::Singleton<ChromotingClientRuntime>::get();
+}
+
+ChromotingClientRuntime::~ChromotingClientRuntime() {}
+
+} // namespace remoting

Powered by Google App Engine
This is Rietveld 408576698