Publishing static pages translate to a more complex admin process, but
much less load on the public side.I love what they do for me,
personally, and use them wherever possible.Embrace the horror :D
Matt Robertson [EMAIL PROTECTED]
MSB Designs,
2) Create actual blank pages on the filesystem named astronomy.cfm, etc
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
Why not include a db field in your cms' page record that is
'FriendlyPageName'. You could then eliminate your need to perform
lookups entirely.
This could also -- depending on your app needs -- allow you to publish
physically discrete, fully or partially static pages where the page name
you
I built a CMS that did this.
All the dynamic content had a static page , this page consisted of metatags,
page title etc. and the page id then a call to a CFC to get the content from
the DB.
Hey presto, static pages for those people that dont like strange urls and it
also has the benefit of
On Friday 10 Oct 2003 14:51 pm, Zimba, Janice C. wrote:
1) Use a url such as www.edu/index.cfm/science/astronomy instead, where
index.cfm will start the ball rolling and run the processes needed.
You can do this, but without the .cfm in the URL, if you like. There was a
recent posting about it
Zimba, Janice C. wrote:
So when a user goes to a url such as www.edu/science/astronomy.cfm the page doesn't really exist.The process will look up the correct document and retrieve the correct content.
4. Use a servlet:
6 matches
Mail list logo
