I'm with Greg for his reasons, and the fact (yes, fact) that xml is stupidly slow to parse compared to the alternative (no tags). If you don't need the conformity xml brings (i.e. standard format across multiple unknown systems), then xml isn't advantageous, regardless of how much hobbit's config files would be easily put into xml.
No offense meant, of course, Galen. I think you're correct that it does make an easy conversion to an xml schema. It just doesn't make sense to make it less readable with such a performance hit.
(I'd still like to see Henrik's take on the idea, though.)
Tod Hansmann Network Engineer
-----Original Message----- From: Hubbard, Greg L [mailto:greg.hubbard at eds.com] Sent: Monday, May 21, 2007 9:24 AM To: hobbit at hswn.dk Subject: RE: [hobbit] xml configs
I vote against this. I LIKE easily understood text files, since I configure Hobbit with a text editor. If there were to be an configuration GUI some day that took over all Hobbit configuration tasks, then I would cease to care how the files are stored.
GLH
-----Original Message----- From: Galen Johnson [mailto:Galen.Johnson at sas.com] Sent: Monday, May 21, 2007 10:08 AM To: hobbit at hswn.dk Subject: [hobbit] xml configs
Hey Henrik,
I know this would be a rather significant change but have you considered switching hobbit to use xml based config files? I'm actually working on an external module that will use an xml config file and thinking about the schema, etc it occurred to me that hobbit would lend itself nicely to xml configs.
Just curious...
=G=
To unsubscribe from the hobbit list, send an e-mail to hobbit-unsubscribe at hswn.dk
To unsubscribe from the hobbit list, send an e-mail to hobbit-unsubscribe at hswn.dk