Adding a SW reporter component updater

chrome/browser/component_updater/sw_reporter_installer_win.h

+// Copyright (c) 2014 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 CHROME_BROWSER_COMPONENT_UPDATER_SW_REPORTER_INSTALLER_WIN_H_
+#define CHROME_BROWSER_COMPONENT_UPDATER_SW_REPORTER_INSTALLER_WIN_H_
+
+class PrefRegistrySimple;
+class PrefService;
+
+namespace component_updater {
+
+class ComponentUpdateService;
+
+// Execute the SwReporter if one is available, otherwise 1) register with the
+// component updater, 2) save a preference in |prefs| identifying that an
+// attempt to execute the reporter tool was made, so that calls to
+// ExecutePending below will be able to continue the work if it doesn't complete
+// before the Chrome session ends. It will also allow the component updater to
+// know if there is a pending execution or not when an update happens.

[Sorin Jianu, 2014/06/20 05:37:39]

Do we need to make any statements about the thread safety of these calls? Are
they only called from the UI thread? If yes, we can say so and add defensive
prog asserts in their implementation. This thought was prompted by seeing the
posts to the file thread in these functions' implementations.

[MAD, 2014/06/20 14:40:15]

Done.

+void ExecuteSwReporter(ComponentUpdateService* cus, PrefService* prefs);
+
+// ExecutePending will only register/execute the SwReporter if a preference is
+// set in |prefs|, identifying that an attempt to register/execute the
+// SwReporter has already been made by calling ExecuteSwReporter above. But only
+// if the max number of retries has not been reached yet.
+void ExecutePendingSwReporter(ComponentUpdateService* cus, PrefService* prefs);
+
+// Register user preferences related to the SwReporter.
+void RegisterPrefsForSwReporter(PrefRegistrySimple* registry);
+
+}  // namespace component_updater
+
+#endif  // CHROME_BROWSER_COMPONENT_UPDATER_SW_REPORTER_INSTALLER_WIN_H_