(1) I would modify the signature to take InputStream and OutputStream objects, resp. This provides for more flexibility in terms of source and destination of the backup data.
well, maybe you need several files to store the data. or maybe a random access file. so streams might also a bit limiting
(2) Initially you mentioned a configuration file for the backup/restore procedures. I suggest you define configuration classes (interfaces), which can load/store themselves to and from streams (yes, I do not like being locked into File instances :-) and to add instances of the toplevel configuration (e.g. BackupConfiguration) as a parameter to the backup/restore methods.
yep. and they probably also encapsulate the exact storage mechanism. -- -----------------------------------------< [EMAIL PROTECTED] >--- Tobias Bocanegra, Day Management AG, Barfuesserplatz 6, CH - 4001 Basel T +41 61 226 98 98, F +41 61 226 98 97 -----------------------------------------------< http://www.day.com >---
