[Chromoting] Introducing refcount-based life time management of the message loops in the service (d…

remoting/base/auto_message_loop.cc

+// Copyright (c) 2012 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/base/auto_message_loop.h"
+
+#include "base/logging.h"
+
+namespace remoting {
+
+AutoMessageLoop::AutoMessageLoop(base::SingleThreadTaskRunner* parent,
+                                 base::SingleThreadTaskRunner* task_runner,
+                                 const base::Closure& stop_callback)
+    : parent_(parent),
+      stop_callback_(stop_callback),
+      task_runner_(task_runner) {
+}
+
+bool AutoMessageLoop::PostDelayedTask(
+    const tracked_objects::Location& from_here,
+    const base::Closure& task,
+    base::TimeDelta delay) {
+  CHECK(task_runner_->PostDelayedTask(from_here, task, delay));

[Wez, 2012/08/28 17:34:53]

Why CHECK rather than returning the result?

[alexeypa (please no reviews), 2012/08/28 19:18:51]

The whole purpose of this class is to make sure that |task_runner_| exists and
running as long as |this| exists. If it CHECKs here it means something is very
wrong about our assumption how shutdown works and it is better to fix it.

+  return true;
+}
+
+bool AutoMessageLoop::PostNonNestableDelayedTask(
+    const tracked_objects::Location& from_here,
+    const base::Closure& task,
+    base::TimeDelta delay) {
+  CHECK(task_runner_->PostNonNestableDelayedTask(from_here, task, delay));

[Wez, 2012/08/28 17:34:53]

Ditto.

[alexeypa (please no reviews), 2012/08/28 19:18:51]

See above.

+  return true;
+}
+
+bool AutoMessageLoop::RunsTasksOnCurrentThread() const {
+  return task_runner_->RunsTasksOnCurrentThread();
+}
+
+void AutoMessageLoop::OnDestruct() const {
+  if (!stop_callback_.is_null())
+    stop_callback_.Run();
+  delete this;
+}
+
+AutoMessageLoop::~AutoMessageLoop() {
+}
+
+}  // namespace remoting