If the info truly is fairly static and almost never changes, there is no
reason to make it database driven / dynamically generated. If they are in
some high-traffic area, hard-coding will also increase efficiency of
serving them to the many hard-traffic people.
However, you have 110 pages today. Are you going to have 220
tomorrow? Are all the pages templated or are you performing a lot of
processing to make each one individual?
One solution is to generate static pages from the database. (I.E. write
a scripts using CFFILE to generate the HTML pages) and then you have the
benefit of static pages and the benefits of a database-driven data. It's
also probably easier than hand-coding all 110 pages.
At 09:18 AM 08/15/2001 -0400, you wrote:
>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/[email protected]/
Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists
