I didn't say anything about the code being unusable. I just meant that in general, placing things like datasources, etc in a configuration file that can be read by all code can enhance reusability if the code is used in another application with, say, a different datasource. Alternately, if the code is ported to a different machine and the datasource changes, you only need to make one change to the config file for all.
Hal Helms "Java for CF Programmers" class in Washington, DC June 23-27 www.halhelms.com -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Todd Sent: Thursday, May 29, 2003 11:34 AM To: [EMAIL PROTECTED] Subject: RE: [CFCDev] CFCs in memory Why is making an app_init.cfc w/ all the settings you need anymore "unusable"? Or, do you mean reusable by other things other than CFMX? ~Todd At 11:30 AM 5/29/2003 -0400, you wrote: >One reason for defining information declaratively in an XML file or ini >file is so that the code itself can be more easily reused. > >Hal Helms >"Java for CF Programmers" class >in Washington, DC June 23-27 >www.halhelms.com ---------- Todd Rafferty ([EMAIL PROTECTED]) - http://www.web-rat.com/ Team Macromedia Volunteer for ColdFusion http://www.macromedia.com/support/forums/team_macromedia/ http://www.devmx.com/ ---------- ---------------------------------------------------------- You are subscribed to cfcdev. To unsubscribe, send an email to [EMAIL PROTECTED] with the word 'unsubscribe cfcdev' in the message of the email. CFCDev is run by CFCZone (www.cfczone.org) and supported by Mindtool, Corporation (www.mindtool.com). ---------------------------------------------------------- You are subscribed to cfcdev. To unsubscribe, send an email to [EMAIL PROTECTED] with the word 'unsubscribe cfcdev' in the message of the email. CFCDev is run by CFCZone (www.cfczone.org) and supported by Mindtool, Corporation (www.mindtool.com).
