LAUGH LAUGH LAUGH... filename is what you may call a level... but what I see is two levels. I am not trying to quip over details... but that seems to be reaching a bit to me.
1. Section 2. Entry In XML you can have attributes and a value for section. You could also have attributes for entry. In the INI file all you can have is data at the second level, and that is it. There is no nesting... just grouped detail. This is one of the reasons people use XML. XML is allows for flexible yet standardized to the task structure. XML is no more a solution in every data/communication task then any Design Pattern is the right way to perform all programming solutions. Also, sometimes there can be more than one way of doing things. What I think the guys are trying to say is for them XML is the best available solution for the task at hand. If you could do it with INI that is fine. They are looking for something more flexible, and it doesn't seem like an INI file is going to get the job done. John -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Joseph Flanigan Sent: Sunday, October 30, 2005 11:48 AM To: [email protected] Subject: RE: [CFCDev] CFSQLTool debate INI is 4 levels: filename.section.entry.value At 08:36 AM 10/30/2005, you wrote: >How structured is the INI option. From what I remember it was not very deep >in scope. XML has attributes, and elements... and it's quite nestable. >Therefore the constraints on a small configuration file or such is quite >flexible in XML. > >John > >-----Original Message----- >From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf >Of Joseph Flanigan >Sent: Sunday, October 30, 2005 4:45 AM >To: [email protected] >Subject: RE: [CFCDev] CFSQLTool debate > > >There is another configuration option that works better in some cases >especially when considering a .INI. style. >Rather than using .INI, use a cfinclude with several CF structures. >This technique works well if there is variant data, like a current >date in the configuration. > > >At 12:23 AM 10/30/2005, you wrote: > > > 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. > > > >As someone who could be accused of being infatuated with XML, I can list > >some justifications for my feelings. > > > >I like using XML in general because I can use it the same way no matter >what > >programming language I'm using. It's portable knowledge, and I can use many > >different tools to work with it. I don't have to worry about parsing or > >validation, that's all taken care of for me. So, while it's more complex, > >most of that complexity is hidden from me and works in my favor, just as >the > >complexity of a car makes it generally easier for me to use than a bicycle, > >which of course is a much simpler machine. > > > > > 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. > > > >That has nothing to do with the file format; you could build a >configuration > >file that contained conditional logic without using XML. That's all up to > >the application reading the file and acting upon that file's data. > > > >Dave Watts, CTO, Fig Leaf Software > >http://www.figleaf.com/ > > > >Fig Leaf Software provides the highest caliber vendor-authorized > >instruction at our training centers in Washington DC, Atlanta, > >Chicago, Baltimore, Northern Virginia, or on-site at your location. > >Visit http://training.figleaf.com/ for more information! > > > > > > > >---------------------------------------------------------- > >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). > > > >An archive of the CFCDev list is available at > >www.mail-archive.com/[email protected] > >----------------------------------------------------------------------- >http://www.switch-box.org/CFSQLTool/Download/ > >Switch_box MediaFirm, Inc. >www.Switch-box.org Loveland, CO USA > > > >---------------------------------------------------------- >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). > >An archive of the CFCDev list is available at >www.mail-archive.com/[email protected] > > > > > > >---------------------------------------------------------- >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). > >An archive of the CFCDev list is available at >www.mail-archive.com/[email protected] ----------------------------------------------------------------------- http://www.switch-box.org/CFSQLTool/Download/ Switch_box MediaFirm, Inc. www.Switch-box.org Loveland, CO USA ---------------------------------------------------------- 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). An archive of the CFCDev list is available at www.mail-archive.com/[email protected] ---------------------------------------------------------- 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). An archive of the CFCDev list is available at www.mail-archive.com/[email protected]
