I guess one of the reasons XML never worked for me is that I see configuration as a type of content which (like any type of content) can be managed using a cms with versioning, auditing, roles based security and the like. I¹ve already written the generic code to allow non-technical users to administrate content of any type. Why not just add configuration data to that list and then just set the permissions to limit it to geeks if they are the only people who should be allowed to change it?!
On 3/26/07 9:57 AM, "Patrick McElhaney" <[EMAIL PROTECTED]> wrote: > On 3/26/07, Tom Chiverton <[EMAIL PROTECTED]> wrote: >> On Sunday 25 Mar 2007, Thomas Messier wrote: >>> > Honestly, most of the time the config files that I work with are simple >>> > enough that they don't warrant validation. >> >> OTOH, maybe someone wants to make a point'n'drool GUI for your config file - >> here having something easily validatable and already machine-readable (i.e. >> XML) pays big. > > Tom, you may be right, but Thomas is right most of the time. :) > > Patrick -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- Reactor for ColdFusion Mailing List [email protected] Archives at: http://www.mail-archive.com/reactor%40doughughes.net/ -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
