I think it is okay to make it static. However just write a publish process
using the existing app and cfhttp to write the generated pages to static
html. Then everytime your database changes just re-run the process.
My 2 cents.
-- Mike
Michael Goodwin
Project Manager
Databuilt, L.L.C.
4720 Salisbury Road,
Suite 213
Jacksonville, FL 32256
(904)493-6157 tel
(904)535-DATA mobile
(904)493-6084 fax
www.databuilt.net
AN E-BUSINESS SOLUTION PROVIDER
-----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/[email protected]/
Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists
