[Chromoting] Let the Windows daemon controller read the unprivileged part of the config without ele…

remoting/host/daemon_controller_common_win.h

Index: remoting/host/daemon_controller_common_win.h
diff --git a/remoting/host/daemon_controller_common_win.h b/remoting/host/daemon_controller_common_win.h
new file mode 100644
index 0000000000000000000000000000000000000000..9334042a95976dc0a7d3436d617f99a2083d7230
--- /dev/null
+++ b/remoting/host/daemon_controller_common_win.h
@@ -0,0 +1,26 @@
+// 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.
+
+#ifndef REMOTING_HOST_DAEMON_CONTROLLER_COMMON_WIN_H_
+#define REMOTING_HOST_DAEMON_CONTROLLER_COMMON_WIN_H_
+
+#include "base/file_path.h"
+
+// Code common to the Windows daemon controller and the Windows elevated
+// controller.
+
+namespace remoting {
+
+// The unprivileged configuration file name.

[alexeypa (please no reviews), 2012/04/24 16:54:56]

nit: Document the location of the file as well.

[simonmorris, 2012/04/25 00:33:32]

Done.

+extern const FilePath::CharType* kUnprivilegedConfigFileName;
+
+// The maximum size of the configuration file. "1MB ought to be enough" for any
+// reasonable configuration we will ever need. 1MB is low enough to make
+// the probability of out of memory situation fairly low. OOM is still possible
+// and we will crash if it occurs.
+extern const size_t kMaxConfigFileSize;
+
+}  // namespace remoting
+
+#endif  // REMOTING_HOST_DAEMON_CONTROLLER_COMMON_WIN_H_