On Thursday 26 April 2007 23:32, Darien Hager wrote: > David Boyes wrote: > >> Brainstorming idea: XML with Schema validation? > >> > >> * The config would be a plain file and portable. > > > > Ugh. "plain XML" is a matter of opinion -- XML of any real complexity > > couldn't be hand-coded. > > Well, myself I have very similar Job and Client definitions for about 60 > machines and using python to generate a config from parsed text files > and applied to templates, so I'm not precisely hand-coding anyway. > > I'd argue that for small set-ups, simply copy-pasting and modifying > given boilerplate will work... and for larger networks you won't want to > deal with the config by hand regardless of how elegant and tersely you > can type it, in which case a well defined config style is an asset. > > Kern Sibbald wrote: > > Thanks for the offer, but unfortunately the answer is no, it is not worth > > exploring for Bacula use. I've mentioned the reasons when this was suggested > > some time ago. > > Oh. Uhm. I tried to find out your reasons back then, except that > SourceForge automatically puts "xml" into most messages as part of it's > recent advertising for DB2. <onomatopoeia>sigh</onomatopoeia> :P
Well, your xml above shows many of the problems that I have with xml :-) 1. it is read only with extreme difficulty by humans (at least by me). 2. the probability of a human (me) updating it correctly in a recovery situation with vi is pretty low. 3. it has enormous bloat -- i.e. to put in a single digit number requires much more space than an ASCII file. I have no problems with putting the bacula conf files in to the database if someone wants to do so. However, I don't foresee any change in the ASCOO format that Bacula requires -- i.e. I don't foresee Bacula reading its conf file directly from an SQL database. So such a program would probably need to be external to Bacula and probably will need to read the current conf format -- at least will need to keep up with the additions/modifications that are made to the conf format (there are a bunch for 2.2.0). A recent feature submission, including the patch, from Jorj Baur could facilitate feeding conf files to the various Bacula components via a pipe. However that code is not yet integrated. I (or someone else) need(s) to modify it to use Bacula internal pipe calls, which are OS "neutral" rather than Unix pipes. > > > --Darien Hager > [EMAIL PROTECTED] > > ------------------------------------------------------------------------- > This SF.net email is sponsored by DB2 Express > Download DB2 Express C - the FREE version of DB2 express and take > control of your XML. No limits. Just data. Click to get it now. > http://sourceforge.net/powerbar/db2/ > _______________________________________________ > Bacula-devel mailing list > [EMAIL PROTECTED] > https://lists.sourceforge.net/lists/listinfo/bacula-devel > ------------------------------------------------------------------------- This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ _______________________________________________ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
