RE: Dynamic page processing
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, Inc.http://mysecretbase.com [Todays Threads] [This Message] [Subscription] [Fast Unsubscribe] [User Settings]
RE: Dynamic page processing
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 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]
RE: Dynamic page processing
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 specify is used in the publishing process. Matt Robertson [EMAIL PROTECTED] MSB Designs, Inc.http://mysecretbase.com [Todays Threads] [This Message] [Subscription] [Fast Unsubscribe] [User Settings]
RE: Dynamic page processing
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 helping your search engine stats (obviously actually having content in a page!) Sections and pages were created by the user hitting a publish button when they were happy with updates, this built the .js files for the navigation and built the staticpages. I quite liked this approach, give it some thought. -Daz -Original Message- From: Zimba, Janice C. [mailto:[EMAIL PROTECTED] Sent: 10 October 2003 14:52 To: CF-Talk Subject: Dynamic page processing Hi, I'm writing a content management system and am trying to determine the best way to start the process of retrieving content.We're using human readable urls, and have a url lookup in the database.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. We've come up with a couple of options to start the process running.The all have pros and cons and I was hoping to get opinions: 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. 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? 3) Use the site wide error handler to capture the 404 error and send it to a custom page which will then start the ball rolling.Would this create an error in the error log for every page anybody ever opens? Thanks for any thoughts and opinions, --Cheers, Janice _ [Todays Threads] [This Message] [Subscription] [Fast Unsubscribe] [User Settings]
Re: Dynamic page processing
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 to this list. Just a varient of SES really. 3) Use the site wide error handler to capture the 404 error and send it to a custom page which will then start the ball rolling.Would this create an error in the error log for every page anybody ever opens? I believe if you trap the error in any way (global error template, try/catch) nothing is logged. -- Tom Chiverton Advanced ColdFusion Programmer Tel: +44(0)1749 834997 email: [EMAIL PROTECTED] BlueFinger Limited Underwood Business Park Wookey Hole Road, WELLS. BA5 1AF Tel: +44 (0)1749 834900 Fax: +44 (0)1749 834901 web: www.bluefinger.com Company Reg No: 4209395 Registered Office: 2 Temple Back East, Temple Quay, BRISTOL. BS1 6EG. *** This E-mail contains confidential information for the addressee only. If you are not the intended recipient, please notify us immediately. You should not use, disclose, distribute or copy this communication if received in error. No binding contract will result from this e-mail until such time as a written document is signed on behalf of the company. BlueFinger Limited cannot accept responsibility for the completeness or accuracy of this message as it has been transmitted over public networks.*** [Todays Threads] [This Message] [Subscription] [Fast Unsubscribe] [User Settings]
Re: Dynamic page processing
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: http://www.newatlanta.com/biz/c/products/bluedragon/self_help/archiveSearch/detail?page=1pagesize=10emailReceivedId=56339 http://www.systemanage.com/presentations/Augmenting_Application.cfm_with_Filters.pdf Jochem [Todays Threads] [This Message] [Subscription] [Fast Unsubscribe] [User Settings]
