> 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.....
Here's an idea - make all of the hyperlinks to the actual HTML page names
and then pour them out of the database when you make an update
That way you can update the main navigation/look&feel centrally and still
keep them as static pages
We have one site like this, but you wouldn't know it was poured
Philip Arnold
Director
Certified ColdFusion Developer
ASP Multimedia Limited
T: +44 (0)20 8680 1133
"Websites for the real world"
**********************************************************************
This email and any files transmitted with it are confidential and
intended solely for the use of the individual or entity to whom they
are addressed. If you have received this email in error please notify
the system manager.
**********************************************************************
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
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
