diff options
| author | 2009-09-21 10:12:59 -0700 | |
|---|---|---|
| committer | 2009-09-21 10:19:17 -0700 | |
| commit | d55e18acbe444b74dc9e71eff6ea2c3eaf25fbd0 (patch) | |
| tree | cdb9404d28612d9bf1d149063cfb515dd9f50161 /libs/ui/FramebufferNativeWindow.cpp | |
| parent | f8d8b46a2c684d51cd661a9d479dd895420a90b2 (diff) | |
Reset backup tracking in response to transport data-wipe notification
When attempting a backup, the transport may inform us that the backend is in an
uninitialized state. This typically means that the device's data has been wiped
after a period [e.g. 90 days] of inactivity. This means that we need to
re-store all data subject to backup, and all of our incremental state tracking
on the device is now stale.
In response, we wipe all of our recorded backup state and restart the backup
pass on all participants.
Diffstat (limited to 'libs/ui/FramebufferNativeWindow.cpp')
0 files changed, 0 insertions, 0 deletions