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 --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-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
