I personally leave everything as .cfm files
and then use cfcache
<cfif isDefined('url.adminflush') AND url.adminflush NEQ "washme">
<cfset cacheoption = "FLUSH">
<cfelse>
<cfset cacheoption = "CACHE">
</cfif>
<cfcache action="#cacheoption#" timeout="#DateAdd("d","-15",Now())#">
----- Original Message -----
From: "Tom Briscoe" <[EMAIL PROTECTED]>
To: "Fusebox" <[EMAIL PROTECTED]>
Sent: Wednesday, April 11, 2001 10:31 AM
Subject: Handling Static and Dynamic Pages
> Hello all. Here's a point I'm pondering and I hope to get your thought
pennies.
>
> When you compose a Fusebox site, it's likely you'll have a large number of
essentially static pages. They're nothing more than content to be displayed
and read. In that case, is it better to:
>
> 1) Stick to Fusebox. Create "dsp_" files and fuseactions for each page to
display.
> 2) Do it the old fashioned way. Create standard pages and link directly
to them. Use Fusebox for site functions that merit it.
>
> Now, let's say we have a compelling reason to make all pages of static
content dynamically generated. (We'll build a content management system to
let Marketing make their own little copy edits rather than bothering you.)
In this case, is it better to:
>
> 1) Use a file-per-page method. Create "dsp_" plus whatever other
appropriate files for each page of content.
> 2) Use a page ID to generate a page. No physical file exists. The page
ID pulls the appropriate text for the page from the database.
>
> I have my own answers. But I'll not spoil it by giving that away yet.
>
> Tom Briscoe
> Web Developer
> Compass Bank
>
>
>
>
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Structure your ColdFusion code with Fusebox. Get the official book at
http://www.fusionauthority.com/bkinfo.cfm
Archives: http://www.mail-archive.com/[email protected]/
Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists
