Introducing the WorkerProcessLauncher class implementing the common logic for spawning a worker pro…

remoting/host/worker_process_launcher_posix.cc

Index: remoting/host/worker_process_launcher_posix.cc
diff --git a/remoting/host/worker_process_launcher_posix.cc b/remoting/host/worker_process_launcher_posix.cc
new file mode 100644
index 0000000000000000000000000000000000000000..5279d2f549cf603f91f4efb18c433161bf37bc9a
--- /dev/null
+++ b/remoting/host/worker_process_launcher_posix.cc
@@ -0,0 +1,19 @@
+// 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.
+//
+// This file implements the Windows service controlling Me2Me host processes
+// running within user sessions.

[Lambros, 2012/03/15 22:24:14]

Drive-by: I don't think we need this class on non-Windows platforms, do we?  On
Linux, we have a script that self-daemonizes, and on Mac the host process will
be managed by launchd.

[alexeypa (please no reviews), 2012/03/15 22:27:12]

Oops. That was a stale comment. I wasn't planning to use this class on Linux or
Mac at the moment but it is nice to have it as an available cross platform
facility.

+
+#include "remoting/host/worker_process_launcher.h"
+
+namespace remoting {
+
+// static
+scoped_ptr<WorkerProcessLauncher> WorkerProcessLauncher::Create(
+    base::MessageLoopProxy* ipc_message_loop) {
+  return scoped_ptr<WorkerProcessLauncher>(
+      new WorkerProcessLauncher(ipc_message_loop));
+}
+
+} // namespace remoting