I worked for a place where they decided to make the pages partly static and
partly dynamic. It was a website that sold movies. Things like the synopsis
and cover art would change rarely, while the pricing could change at any
time. What we did was give the staff the ability to regenerate the static
page (if they changed something like the synopsis) on demand. The built page
then contains only one query that does a price lookup, as that was the only
data that needed to be current at all times. It's a lot less load then
having a dynamic page do ten queries whenever someone looks up a title.
Melanie
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
