572
edits
Changes
Features/Backup and Restore/Enhancements (view source)
Revision as of 20:45, 12 November 2013
, 20:45, 12 November 2013no edit summary
* 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.
* 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.
== Format ==
* As mentioned before current implementation of backup-to-memory-stick simple creates a compressed tarfile of the datastore directory. Are we going to continue with this approach, or we can think of something that will allow us to be more flexible about the contents being backup'd.
== Difficulties ==
== Difficulties ==