diff options
| author | rlarocque@chromium.org <rlarocque@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2013-05-10 19:26:16 +0000 |
|---|---|---|
| committer | rlarocque@chromium.org <rlarocque@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2013-05-10 19:26:16 +0000 |
| commit | e85797cd8652628481291a6c202e150d1f8adf78 (patch) | |
| tree | d1b2e3441d5e79c60b9e95c11b36aa5177e668b4 /chrome/browser/invalidation/OWNERS | |
| parent | edfdd0d4d3dd10f5c0f3f9de204961191656878f (diff) | |
| download | chromium_src-e85797cd8652628481291a6c202e150d1f8adf78.zip chromium_src-e85797cd8652628481291a6c202e150d1f8adf78.tar.gz chromium_src-e85797cd8652628481291a6c202e150d1f8adf78.tar.bz2 | |
Commit InvalidationService implementations
This commit introduces a new ProfileKeyedService, the
InvalidationService. Clients may register with this service to receive
notifications from a server informing them when they need to fetch
updates to their cached state. (In other words, they will receive
notifications when their cache has become invalid.)
There are three different implementations of this service, all of which
inherit from InvalidationFrontend. The current provider of
invalidations, ProfileSyncService, also inherits from this interface.
The TiclInvalidationService receives notifications through the C++
version of the googlecacheinvalidation (aka. TICL) library. It is used
on Chromium for Desktop operating systems.
The AndroidInvalidationService receives notifications by listening to
the in-process NotificationService
(content/public/browser/notification_service.h). The code that actually
sends these notifications is a small bridge from Java-land, which is not
affected by this CL.
The P2PInvalidationService uses XMPP peer-to-peer connections to send
and receive invalidations. This has not been used in Chromium for a
very long time. We keep it around because some of our integration
tests rely on it.
This CL also includes an InvalidationServiceFactory to help manage the
selection and construction of these InvalidationServices.
The tests for these new services are based on a modified version of
sync/notifier/invalidator_test_template.h. The P2PInvalidationService
is not tested at all because it is itself a test-only utility.
In addition to the new code, this CL moves around some old code to help
populate a new directory, chrome/browser/invalidation. We're trying to
separate invalidations from sync, so the
chrome/browser/sync/invalidations directory was no longer needed.
Finally, note that this commit does not change Chromium in any way. It
adds new classes and test for them, but the rest of the code has not
been modified to make use of them. Those changes will happen in a
future CL.
BUG=124137
Review URL: https://chromiumcodereview.appspot.com/13991017
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@199520 0039d316-1c4b-4281-b951-d872f2087c98
Diffstat (limited to 'chrome/browser/invalidation/OWNERS')
| -rw-r--r-- | chrome/browser/invalidation/OWNERS | 5 |
1 files changed, 5 insertions, 0 deletions
diff --git a/chrome/browser/invalidation/OWNERS b/chrome/browser/invalidation/OWNERS new file mode 100644 index 0000000..e838315 --- /dev/null +++ b/chrome/browser/invalidation/OWNERS @@ -0,0 +1,5 @@ +akalin@chromium.org +dcheng@chromium.org +nyquist@chromium.org +rlarocque@chromium.org +tim@chromium.org |