The way to make it work is to stop writing static HTML sites. Instead
use one of the many freely available open source CMS frameworks and
simply hand code the templates for them once (making hand coded changes
for other customer sites as required). That's what we do with Drupal.
I would not recommend this for sites on shared servers unless they really do
need a full-featured CMS.
Speed is important .. why add bloat if its not needed?
A mysql server in a typical ISP shared hosting environment often struggles
to handle a large number of statements per second
from hundreds of sites .. especially when some of the sites are being hit
hard by crawlers.
..most off-the-shelf CMS do way too many lookups to show even a simple page
Drupal, Wordpress and Joomla are very bad in this regard (doing around 15-40
mysql lookups for each page!)
... Xoops seems better with its file-based caching but may still be
overkill in a lot of cases.
A lot of this waste comes from storing stats in mysql, looking up user data,
etc ...
(and in some cases attempting to use mysql even for caching! bad.. bad..
bad..)
If you are not using user logins then why do all those extra lookups?
I think part of the problem might be that a lot of CMS developers are not
testing on busy shared servers or high-traffic sites.
(they are probably only testing on dedicated servers where they have mysql
to themselves and the bottlenecks might be elsewhere)
I'm not going to tell people to spend extra cash for a dedicated server if
all they want is a few simple "static" pages.
*******************************************************************
List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm
Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm
Help: [EMAIL PROTECTED]
*******************************************************************
