> As an alternative, what I generally recommend for machine-specific
> application settings is that you store them on the machine itself,
> and have your application read those values from wherever you've
> stored them. You could store them in a text file, or within the
> registry, for example. If you store them in a file, make sure that
> file doesn't get overwritten when you move a new build of your
> application from development to production.
>
> Dave Watts, CTO, Fig Leaf Software
Thanks. That's a good suggestion. It still requires maintaining 3
separate instances of the same info in different locations but it
would be less volatile data and would be easier to maintain than
trying to juggle separate application.cfm files.
Stephen
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Structure your ColdFusion code with Fusebox. Get the official book at
http://www.fusionauthority.com/bkinfo.cfm
Archives: http://www.mail-archive.com/[email protected]/
Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists
