Android/frameworks_base
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Add android.backup.BackupManager

Browse Source 
Also tweak the dataChanged() api to have the client supply a package name.  We
don't necessarily TRUST this, but we use it to narrow the set of packages requesting
a backup pass, no longer blithely scheduling a pass for all packages associated
with the caller's uid.
This commit is contained in:
Christopher Tate
2009-04-30 11:36:21 -07:00
parent 487529a70c
commit a8bf815c61
5 changed files with 123 additions and 6 deletions
Download Patch File Download Diff File Expand all files Collapse all files

12
services/java/com/android/server/BackupManagerService.java
View File

@@ -164,7 +164,7 @@ class BackupManagerService extends IBackupManager.Stub {
// ----- IBackupManager binder interface -----
public void dataChanged() throws RemoteException {
public void dataChanged(String packageName) throws RemoteException {
// Record that we need a backup pass for the caller. Since multiple callers
// may share a uid, we need to note all candidates within that uid and schedule
// a backup pass for each of them.
@@ -173,10 +173,14 @@ class BackupManagerService extends IBackupManager.Stub {
if (targets != null) {
synchronized (mQueueLock) {
// Note that this client has made data changes that need to be backed up
// !!! add them to the set of pending packages
for (ServiceInfo service : targets) {
if (mPendingBackups.add(service)) {
// !!! TODO: write to the pending-backup journal file in case of crash
// validate the caller-supplied package name against the known set of
// packages associated with this uid
if (service.packageName.equals(packageName)) {
// add the caller to the set of pending backups
if (mPendingBackups.add(service)) {
// !!! TODO: write to the pending-backup journal file in case of crash
}
}
}