diff options
| author | maxbogue <maxbogue@chromium.org> | 2014-09-29 10:45:19 -0700 |
|---|---|---|
| committer | Commit bot <commit-bot@chromium.org> | 2014-09-29 17:45:32 +0000 |
| commit | b8d6efcb29ede4dd881700526930b75a077f9a4e (patch) | |
| tree | 9f19023c3314ba7c1ed14bb3380e88947df94057 /chrome/android/DEPS | |
| parent | 1c629b00ea176d1ffd8dcb97356efe3f60d2916b (diff) | |
| download | chromium_src-b8d6efcb29ede4dd881700526930b75a077f9a4e.zip chromium_src-b8d6efcb29ede4dd881700526930b75a077f9a4e.tar.gz chromium_src-b8d6efcb29ede4dd881700526930b75a077f9a4e.tar.bz2 | |
Massive refactor of the Android invalidation code.
We want the invalidations code to exist as a component
independent of sync (see bug). This CL seeks to move toward
that for the Android invalidations codebase.
Generally, things moved from //chrome/browser/invalidation
to //components/invalidation, even if git didn't mark them
as moves.
To accomplish this, I had to unify where the JNI occurred.
In Java, InvalidationService was renamed to
InvalidationClientService as the class that communicates
with GCM.
A new InvalidationService class was introduced to handle JNI
and other Java entry points to the component. Several
methods from ProfileSyncService and InvalidationController
moved to it.
InvalidationController is now the bridge between sync and
the invalidation component, and has no JNI nor C++
counterpart.
InvalidationServiceFactory was added to assist in the
creation and management of InvalidationService objects
across the JNI boundary.
BUG=259559
Review URL: https://codereview.chromium.org/459513002
Cr-Commit-Position: refs/heads/master@{#297202}
Diffstat (limited to 'chrome/android/DEPS')
| -rw-r--r-- | chrome/android/DEPS | 1 |
1 files changed, 1 insertions, 0 deletions
diff --git a/chrome/android/DEPS b/chrome/android/DEPS index c80012b5..32b2fa6 100644 --- a/chrome/android/DEPS +++ b/chrome/android/DEPS @@ -1,3 +1,4 @@ include_rules = [ + "+components/invalidation", "+jni", ] |