summaryrefslogtreecommitdiffstats
path: root/chrome/common/chrome_switches.cc
diff options
context:
space:
mode:
authorrlarocque@chromium.org <rlarocque@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98>2013-06-29 01:45:09 +0000
committerrlarocque@chromium.org <rlarocque@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98>2013-06-29 01:45:09 +0000
commitdbbec3a0133edaff11b16c6bc3fd73aac8ab4e31 (patch)
tree20b4a2df530ac7c83bcc5e7d460137e97846685e /chrome/common/chrome_switches.cc
parentc146a323f91c8376afe55c93c6a31df0075be62b (diff)
downloadchromium_src-dbbec3a0133edaff11b16c6bc3fd73aac8ab4e31.zip
chromium_src-dbbec3a0133edaff11b16c6bc3fd73aac8ab4e31.tar.gz
chromium_src-dbbec3a0133edaff11b16c6bc3fd73aac8ab4e31.tar.bz2
Use InvalidationService (retry of r208315)
The InvalidationService was introduced r199520. That commit added the InvalidationService interface and several implementations of it, but made no use of the new code. This commit builds on that work. Up until now, TICL invalidations were handled on the sync thread. The related objects were instantiated and owned by the SyncBackendHost and SyncManager. All requests to update the set of object registrations had to be passed to the sync thread. Components that wanted to receive invalidations but were not part of sync had to route their communication with the invalidations server through ProfileSyncService to get to the sync thread. Things were a bit different on Android, but the system still tried to pretend that invalidations were owned by the sync thread. The new InvalidationService implementation is a ProfileKeyedService that is mostly independent from sync. It still relies on sync to manage sign in and fetch the appropriate auth tokens. However, it's now much easier for components outside of sync to communication with the invalidations server. The new system allows us to remove a lot of invalidations-related code from the ProfileSyncService, SyncBackendHost and SyncManager. Sync is now just one of many clients of the InvalidationService. The SyncBackendHost is responsible for forwarding messages back and forth between the InvalidationService and the sync thread. TBR=dcheng,satorux1,battre,rsimha,bauerb,sky,erg BUG=124137 Review URL: https://chromiumcodereview.appspot.com/17699005 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@209264 0039d316-1c4b-4281-b951-d872f2087c98
Diffstat (limited to 'chrome/common/chrome_switches.cc')
-rw-r--r--chrome/common/chrome_switches.cc3
1 files changed, 0 insertions, 3 deletions
diff --git a/chrome/common/chrome_switches.cc b/chrome/common/chrome_switches.cc
index 3533889..c83bf76 100644
--- a/chrome/common/chrome_switches.cc
+++ b/chrome/common/chrome_switches.cc
@@ -1337,9 +1337,6 @@ const char kSyncKeystoreEncryption[] = "sync-keystore-encryption";
const char kSyncShortInitialRetryOverride[] =
"sync-short-initial-retry-override";
-// Overrides the default notification method for sync.
-const char kSyncNotificationMethod[] = "sync-notification-method";
-
// Overrides the default host:port used for sync notifications.
const char kSyncNotificationHostPort[] = "sync-notification-host-port";