From: Carlos H. C. <li...@wa...> - 2009-11-19 12:11:06
|
PC> Except few information areas that are repeating patterns (list of PC> web resources, news, sub-projects and members information) nothing PC> really calls for a database. Database would be an overkill for PC> this, period. These few info bits that *could* be served from PC> database are few, so having them in "data text files" is cheaper PC> and quicker. I'll report my experience, with both cases. My FireBase portal started as static pages. The change for dynamic pages with content retrieved from a DB was a huge facilitator for me. Updating the site (aka. inserting news, articles, links or anything else) became a matter of starting a small Delphi app and inserting the content into the appropriate place (DB table), just that! Right now, FireBase uses PHP with direct access to FB database and it was really easy to be implemented (I never had programmed in PHP before that). Most difficult task (for me) was/is the webdesign. So, FirebirdSQL has news? Yes. Does it has articles (docs)? Yes, Does it has Download area? Yes. So, imho, this is enough to justify using a DB backend and dynamic pages. Also, DB backend makes it much easier to implement RSS feeds. Nowadays, this is one of the best ways to keep people updated, and a must for any decent site. Just my 2c. []s Carlos H. Cantu www.FireBase.com.br - www.firebirdnews.org www.warmboot.com.br - blog.firebase.com.br |