when the content is created, then use application.cfm to get the ball
rolling. Is there much, if any, overhead in using the application.cfm
file in this manner?
A variant of this approach that is used by content management systems
like CommonSpot (http://www.paperthin.com <http://www.paperthin.com/> )
is to have �stub� pages which set up various variables etc. that the
framework uses e.g. have an astronomy.cfm stub page which simply
includes/redirects/modules the actual content. This requires the
publishing and synchronizing of these stub pages when content is being
added/updated but you can utilize this to your advantage by allowing
them to cache various page settings.
This approach is somewhere in between having fully published static
pages which are very fast to serve and fully dynamic pages which are
always up to date but draining on the server.
André
[Todays Threads] [This Message] [Subscription] [Fast Unsubscribe] [User Settings]
