> > The only real problem is that if one developer writes bad
> > code, you'll have to cycle the service for everybody.
>
> That sounds like a pretty big problem to me!
It's actually not that bad.
> I appreciate your suggestions, and I will try to incorporate
> a few. Our situation is that this is not a new development project.
> We have inherited code from a previous developer who, evidently,
> either had some other system for managing development environments
> or (more than likely) had no regard for these issues. As a result,
> there are a lot of pre-existing problems which would make it
> difficult to do things as you describe.
It's usually not that difficult to fix an application to fit this model,
though. For example, if the application relies on the root slash mapping in
the CF Administrator for resolving absolute CFINCLUDE and CFMODULE template
paths, this won't work on a development server, because there will probably
be multiple virtual web servers running, and the root slash can't be used
more than once. To fix this, you simply create a mapping for that
application, and do a global replace to fix the problem.
Dave Watts, CTO, Fig Leaf Software
http://www.figleaf.com/
voice: (202) 797-5496
fax: (202) 797-5444
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Structure your ColdFusion code with Fusebox. Get the official book at
http://www.fusionauthority.com/bkinfo.cfm
------------------------------------------------------------------------------
Archives: http://www.mail-archive.com/cf-linux%40houseoffusion.com/
To Unsubscribe visit
http://www.houseoffusion.com/index.cfm?sidebar=lists&body=lists/cf_linux or send a
message to [EMAIL PROTECTED] with 'unsubscribe' in the body.
