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]
