G'day Chris, Actually nothing wrong with that. It's how I've done it up till now for a decade.
Except I'm wanting to learn more about XML than i currently do, and I have a series of sites to build now that have the same structure, but different settings for the specific The point of using a XML file is that's where the differences in setup between one site and another would be, so the Application.cfc stays stable, or as you say all that would be achieved would be a doubling of the files to be maintained. I've found as Application.cfc files have got more and more complex that its easier and easier to forget to set something and I was tinkering about with pulling out all the site-specific settings in to a single file (the XML file) and have a local XML file and a production XML file Cheers Mike Kear Windsor, NSW, Australia Certified Advanced ColdFusion Developer AFP Webworks http://afpwebworks.com ColdFusion, PHP, ASP, ASP.NET hosting from AUD$15/month On 4/30/06, Chris Velevitch <[EMAIL PROTECTED]> wrote: > On 4/30/06, Mike Kear <[EMAIL PROTECTED]> wrote: > > I'm experimenting about with using an XML file for many of the > > configuration items specific to a site (dsn, paths, etc) and wondered > > at what point is the best to have Application.cfc read the XML file > > What's wrong with using Application.cfc to set up the config items? > Saves you from having to maintain 2 files. > > > Chris > -- > Chris Velevitch > Manager - Sydney Flash Platform Developers Group > www.flashdev.org.au > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Message: http://www.houseoffusion.com/lists.cfm/link=i:4:239134 Archives: http://www.houseoffusion.com/cf_lists/threads.cfm/4 Subscription: http://www.houseoffusion.com/lists.cfm/link=s:4 Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4 Donations & Support: http://www.houseoffusion.com/tiny.cfm/54
