The one problem I have with deploying configuration information in CF is that the administrator I'm delivering it to then has to edit CF.
Sure, CF is easy - plain text is easier. I'm not saying XML is the end all be all of configuration files. I like .ini files with name value pairs, or whatever configuration system is best for that application (gasp, i have even put some configuration info in the database before and cached it on the initial hit and provided a web interface to update said data.) However, a database is obviously not the best place to store framework configuration data - which is the point Joe initially made when he suggested a better alternate to XML. At this point most of the people (other than Joe) are arguing for the same side of the fence really. We all prefer to store configuration data in a text file; be that an ini file, an xml file, a CF file, etc. as opposed to in the database. What I haven't really heard is a reason for this thread to continue :O) I hate to complain because some of the venom has been fun to read - but really, nothing is being gained here and, at this point, the entire thread is WAY off topic for a CFC development list. (a cf list, perhaps not, but CFC list - definitely) Cheers, Bill On 10/28/05, Marlon Moyer <[EMAIL PROTECTED]> wrote: > Patrick, I'll back you up on this. I don't necessarily see a problem > with having configuration information in an xml file, but better > alternatives could exist. I do think it's a little odd to have the > program flow stored in XML though. > > I think you're right about CF programmers falling in love with XML. > Why is it that the FB, MG, and M2 crowds love having it for their > controller definitions. It's not any easier than CF , and I would > argue that it's probably a little more complicated. It's just as easy > to edit CF code with notepad as it is to edit CF code. > > I did hear a good quote the other day: "A programmer runs into a > problem and decides to use XML for the solution. Now he has two > problems." > > > > > > On 10/28/05, Patrick McElhaney <[EMAIL PROTECTED]> wrote: > > On 10/28/05, Joseph Flanigan <[EMAIL PROTECTED]> wrote: > > > I did not mean to stir-up a discussion on Mach, I was using one > > > aspect of Mach, XML, as something I think is wrong. > > > > I must jump to Joseph's defense here. I think ColdFusion framework > > developers became infatuated with XML a few years ago -- starting with > > XML fusedocs -- and it's gotten out of hand. > > > > I don't understand what was wrong with simpler text-based formats, > > such as the java properties file and windows ini file. I thought that > > a config file should only specify details; it should not implement > > business logic. And I thought that's why config file formats tended to > > be so constrained. The idea of an eXtensible format for config files > > seems backwards to me. > > > > If Joseph is an intelligent contributer who questions long-held > > beliefs with sound arguments, I think he's an asset to the community. > > If he's a troll, please don't feed him. > > > > Patrick > > > > > > > > -- > > Patrick McElhaney > > 704.560.9117 > > http://pmcelhaney.weblogs.us > > > > > > ---------------------------------------------------------- > > You are subscribed to cfcdev. To unsubscribe, send an email to > > [email protected] with the words 'unsubscribe cfcdev' as the subject of > > the email. > > > > CFCDev is run by CFCZone (www.cfczone.org) and supported by CFXHosting > > (www.cfxhosting.com). > > > > CFCDev is supported by New Atlanta, makers of BlueDragon > > http://www.newatlanta.com/products/bluedragon/index.cfm > > > > An archive of the CFCDev list is available at > > www.mail-archive.com/[email protected] > > > > > > > > > -- > Marlon > > "And I Sleep, and I dream of the person I might have been, and I'll be > free again > And I Speak, like someone who's been to the highest peaks, and back again > And I Swear, that my grass is greener than anyones, until I believe again" > > > ---------------------------------------------------------- > You are subscribed to cfcdev. To unsubscribe, send an email to > [email protected] with the words 'unsubscribe cfcdev' as the subject of the > email. > > CFCDev is run by CFCZone (www.cfczone.org) and supported by CFXHosting > (www.cfxhosting.com). > > CFCDev is supported by New Atlanta, makers of BlueDragon > http://www.newatlanta.com/products/bluedragon/index.cfm > > An archive of the CFCDev list is available at > www.mail-archive.com/[email protected] > > > -- [EMAIL PROTECTED] http://blog.rawlinson.us If you want Gmail - just ask. ---------------------------------------------------------- You are subscribed to cfcdev. To unsubscribe, send an email to [email protected] with the words 'unsubscribe cfcdev' as the subject of the email. CFCDev is run by CFCZone (www.cfczone.org) and supported by CFXHosting (www.cfxhosting.com). CFCDev is supported by New Atlanta, makers of BlueDragon http://www.newatlanta.com/products/bluedragon/index.cfm An archive of the CFCDev list is available at www.mail-archive.com/[email protected]
