Well, what he's asking for is not insane. In fact, it really makes a
lot of sense - don't make things dynamic that are not dynamic. I know
of a lot of people that are reverting to static, or "semi-static" pages
from dynamic pages - especially for pages that really have no reason to
be dynamic. Its all for scalability reasons.
Having said that, you don't really have to change much. There are a lot
of ways of doing what he wants without much work.
One way is to just "spider" over the files and save them as HTML files.
That way, if they change, just run the spider again. You could set the
scheduler to do it for you. You could use a program like Teleport Pro
to do it as well.
Another way might be to use the CFCACHE tag - this might take care of
everything for you, depending on your situation.
So, in my opinion, its not a bad idea for the pages to be just HTML
pages. To recode them by hand is crazy, but to use the system you
already have in place, and just "cache" the pages as HTML pages for an
indefinate period is the right way to go.
Michael Ross 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/cf-talk@houseoffusion.com/
Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists
