History log of /frameworks/base/core/jni/android_backup_BackupDataInput.cpp
Revision Date Author Comments (<<< Hide modified files) (Show modified files >>>)
4528186e0d65fc68ef0dd1941aa2ac8aefcd55a3 06-Mar-2010 Christopher Tate <ctate@google.com> Refactor android.backup => android.app.backup

Change-Id: I0b21316ff890d7f3c7d4b82837bb60670724c2e8
/frameworks/base/core/jni/android_backup_BackupDataInput.cpp
5f15d151b5101fadfe6cba1e8f4aa6367e8c603e 16-Jun-2009 Joe Onorato <joeo@android.com> checkpoint BackupDatAInput / RestoreHelper
/frameworks/base/core/jni/android_backup_BackupDataInput.cpp
2fdd428e0f18384160f7c38ce3a2cd9ba7e7b2c2 13-Jun-2009 Christopher Tate <ctate@google.com> Fix some backup reader/writer issues; make local transport do backup

As of this change, LocalTransport is successfully propagating data changes from
the backup data format into a repository stored in /cache/backup/[packagename].
Each backup key gets a separate file there for ease of manipulation and testing.

The general semantics of BackupDataReader have been tweaked, too; it now just
returns simple "we're done with the data" when it hits the end, even if no
footer has been found, because on the writing side the footer isn't being
written. Also, reading an entity now merely requires a "big enough" buffer, not
an exactly-sized one.

This is all a work in progress, but this is at least working now for purposes of
this local transport.

Still to do: proper change vs deletion detection, as well as expanding the data
format itself to include necessary metadata etc.
/frameworks/base/core/jni/android_backup_BackupDataInput.cpp
03f4df4b3bf8b8828e795a0bf1f913e6e08f12f1 13-Jun-2009 Joe Onorato <joeo@android.com> Fix the jni initializer.
/frameworks/base/core/jni/android_backup_BackupDataInput.cpp
1cf587496fcb1d652bab9fc6792fb106b6fefaa4 12-Jun-2009 Joe Onorato <joeo@android.com> Add RestoreFileHelper, BackupDataInput, and add java wrappers for the methods on BackupDataOutput.
/frameworks/base/core/jni/android_backup_BackupDataInput.cpp