summaryrefslogtreecommitdiffstats
path: root/chrome/installer/util/google_update_settings.h
diff options
context:
space:
mode:
authornsylvain@chromium.org <nsylvain@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98>2010-09-07 05:15:21 +0000
committernsylvain@chromium.org <nsylvain@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98>2010-09-07 05:15:21 +0000
commitd54636e5c569acc5acc618b0ea10b2a565514c75 (patch)
tree830f6036ec2d1f1a371a74f41c56d37ef1a3c64e /chrome/installer/util/google_update_settings.h
parent2ccb70ec0356cb9257ce62958e37ec19c1b7c32c (diff)
downloadchromium_src-d54636e5c569acc5acc618b0ea10b2a565514c75.zip
chromium_src-d54636e5c569acc5acc618b0ea10b2a565514c75.tar.gz
chromium_src-d54636e5c569acc5acc618b0ea10b2a565514c75.tar.bz2
Revert 58639 -
This seems to have caused some ui_tests to fail (AllowCookies, BlockCookies) Original comment: Write the outcome of the Toast Experiment for system-level installs to the right registry key. BUG=44378 TEST=None Review URL: http://codereview.chromium.org/3308003 TBR=finnur@chromium.org Review URL: http://codereview.chromium.org/3369002 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@58667 0039d316-1c4b-4281-b951-d872f2087c98
Diffstat (limited to 'chrome/installer/util/google_update_settings.h')
-rw-r--r--chrome/installer/util/google_update_settings.h19
1 files changed, 1 insertions, 18 deletions
diff --git a/chrome/installer/util/google_update_settings.h b/chrome/installer/util/google_update_settings.h
index 715ef9f..6e12cb66 100644
--- a/chrome/installer/util/google_update_settings.h
+++ b/chrome/installer/util/google_update_settings.h
@@ -1,4 +1,4 @@
-// Copyright (c) 2010 The Chromium Authors. All rights reserved.
+// Copyright (c) 2006-2008 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.
@@ -105,23 +105,6 @@ class GoogleUpdateSettings {
int install_return_code,
const std::wstring& value);
- // For system-level installs, we need to be able to communicate the results
- // of the Toast Experiments back to Google Update. The problem is just that
- // the experiment is run in the context of the user, which doesn't have
- // write access to the HKLM key that Google Update expects the results in.
- // However, when we are about to switch contexts from system to user, we can
- // duplicate the handle to the registry key and pass it (through handle
- // inheritance) to the newly created child process that is launched as the
- // user, allowing the child process to write to the key, with the
- // WriteGoogleUpdateSystemClientKey function below.
- static int DuplicateGoogleUpdateSystemClientKey();
-
- // Takes a |handle| to a registry key and writes |value| string into the
- // specified |key|. See DuplicateGoogleUpdateSystemClientKey for details.
- static bool WriteGoogleUpdateSystemClientKey(int handle,
- const std::wstring& key,
- const std::wstring& value);
-
// True if a build is strictly organic, according to its brand code.
static bool IsOrganic(const std::wstring& brand);