Assuming there's no need for personalization or much in the way of security,
it should work fine and avoid any performance hit of the CF/DB calls. Just
use CF to generate the static files and keep the manager happy. If they've
built content management/editing into the back end they can still use it
when content changes are needed and then re-publish the site. Of course,
setting up static page publishing system gives the developer a new project
to enjoy. :)
Or is the manager saying they literally want them hand-coded manually?
Ken
-----Original Message-----
From: Michael Ross [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, August 15, 2001 9:18 AM
To: CF-Talk
Subject: Thoughts
I think I know what everyone has to say about this but I thought I would
share. A web manager here has asked one of the developers to change an app
they built. The current one is all db driven, it has a few pages to display
about 110 pages worth of info. Well the manager wants them to make all the
pages static. To have them hard coded. The manager says that because the
info is only updated once in a blue moon they don't need the extra calls to
the db. Well the developer called me to find out where they could find info
on why this would be a bad idea.....
any thoughts!!!!
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Structure your ColdFusion code with Fusebox. Get the official book at
http://www.fusionauthority.com/bkinfo.cfm
FAQ: http://www.thenetprofits.co.uk/coldfusion/faq
Archives: http://www.mail-archive.com/cf-talk@houseoffusion.com/
Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists
