572
edits
Changes
Jump to navigation
Jump to search
Line 17:
Line 17: +
Features/Backup and Restore/Enhancements (view source)
Revision as of 21:18, 12 November 2013
, 21:18, 12 November 2013→Back-ends
* Currently, the actual backup and restore code only handles the interface. The back-end scripts are completely separated packages from Sugar. The only two back-ends are: (a) dsd rsync-based scripts alias backup-to-xs and (b) Martin Abente and Esteban Arias scripts for compressing and copying to the back-end, alias backup-to-memory-stick.
* Currently, the actual backup and restore code only handles the interface. The back-end scripts are completely separated packages from Sugar. The only two back-ends are: (a) dsd rsync-based scripts alias backup-to-xs and (b) Martin Abente and Esteban Arias scripts for compressing and copying to the back-end, alias backup-to-memory-stick.
* One of the enhancements ideas is to move this code to Sugar by defining an abstract class or template for implementing backup and restore back-ends. This template should handle the interactions defined by the Triggering methods and Progress dialog.
* One of the enhancements ideas is to move this code to Sugar by defining an abstract class or template for implementing backup and restore back-ends. This template should handle the interactions defined by the Triggering methods and Progress dialog.
* We should start by something simple like backup-to-memory-stick, but we could already have something in mind, based on web services and see if its makes sense under that scenario.
== Difficulties ==
== Difficulties ==