Refactoring Native Messaging Host process launching code into its own file.

remoting/host/win/launch_native_messaging_host_process.h

+// 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.
+
+#ifndef REMOTING_HOST_WIN_LAUNCH_NATIVE_MESSAGING_HOST_PROCESS_H_
+#define REMOTING_HOST_WIN_LAUNCH_NATIVE_MESSAGING_HOST_PROCESS_H_
+
+#include <cstdint>
+
+#include "base/win/scoped_handle.h"
+
+namespace base {
+class FilePath;
+}  // namespace base
+
+namespace remoting {
+
+// Launches the executable at |binary_path| using the parameters passed in.
+// If the process is launched successfully, |read_handle| and |write_handle| are
+// valid for I/O and the function returns 0.  Otherwise a non-zero Windows error
+// code is returned.
+uint32_t LaunchNativeMessagingHostProcess(

[Sergey Ulanov, 2016/07/28 23:57:15]

Return bool instead of uint32_t?
The actual error code is not used by the caller. If the error code is useful
then maybe use int, intead of int32_t?

[joedow, 2016/07/29 03:32:56]

I need at least three states (success, failure, cancelled) so I will simlpify
the return value but use an enum instead of a bool.

+    const base::FilePath& binary_path,
+    intptr_t parent_window_handle,
+    bool elevate_process,
+    base::win::ScopedHandle* read_handle,
+    base::win::ScopedHandle* write_handle);
+
+}  // namespace remoting
+
+#endif  // REMOTING_HOST_WIN_LAUNCH_NATIVE_MESSAGING_HOST_PROCESS_H_