CMS Advice
Posted: Wed Jun 05, 2002 10:44 am
hey,
I am beginning development of a content management application for my organization's extra/intranet and i am looking for a little feedback on my approach. Particulary dynamic vs. generated pages.
There are two methods i am considering:
1- when users create or update pages, all data goes into the database and waits for approval. once changes are approved, the page is marked as 'live'. each time a visitor requests the page it is built on-the-fly and sent to the browser.
2- when users create or update pages, all data goes into the database and waits for approval. once changes are approved, the a (technically) static page is created on the server. This page can/will still contain some dynamic elements (current date, announcements, etc... small stuff)
i am currently leaning towards the second approach, as i am unsure of the level of traffic we will be getting, and this seems like it would be lighter on the database server, and faster.
i'd appreciate any feedback on this.
-c.w.collins
I am beginning development of a content management application for my organization's extra/intranet and i am looking for a little feedback on my approach. Particulary dynamic vs. generated pages.
There are two methods i am considering:
1- when users create or update pages, all data goes into the database and waits for approval. once changes are approved, the page is marked as 'live'. each time a visitor requests the page it is built on-the-fly and sent to the browser.
2- when users create or update pages, all data goes into the database and waits for approval. once changes are approved, the a (technically) static page is created on the server. This page can/will still contain some dynamic elements (current date, announcements, etc... small stuff)
i am currently leaning towards the second approach, as i am unsure of the level of traffic we will be getting, and this seems like it would be lighter on the database server, and faster.
i'd appreciate any feedback on this.
-c.w.collins