<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 TRANSITIONAL//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; CHARSET=UTF-8">
<META NAME="GENERATOR" CONTENT="GtkHTML/3.32.2">
</HEAD>
<BODY>
True...static pages do not need dynamic content. The DB was used for the content not the template. Templates were usually XHTML and the content was in mySQL. <BR>
<BR>
My key point here is just that one should know the code. Not rely on a program to do it for you...<BR>
<BR>
Many ways to get there from here and CMS platforms exist for a reason. I just have always taught, "know the code first, then use the tools..."<BR>
<BR>
RinL<BR>
<BR>
On Tue, 2011-12-13 at 09:56 -0500, Michael B. Trausch wrote:
<BLOCKQUOTE TYPE=CITE>
<PRE>
For content that is mostly static, though, that's overkill; hitting a
database to serve up a site's primary landing page and such can make the
difference between your home page being up or not when your database
server is really busy. If you're on some sort of shared hosting that
problem becomes somewhat unpredictable, so it's good to have at least
the common pages that aren't edited frequently be some sort of
relatively static content.
Of course, I realize that many sites aren't like that, and there are
solutions to the problem by using reverse proxies, multiple Web servers,
caching systems like memcached, and so forth, but for most things I've
done, it's easier to have the "front" pages for the site be nothing more
than templates that don't need to interact with a database.
It's something of a happy medium between 100% static pages and a CMS.
There is also the possibility of using something like m4 to generate a
lot of static .html pages from templates and inclusion directives, or a
dedicated tool for the job. I know that there is at least one out there
that is designed to be used for publishing a blog and it will "compile"
the blog site to a bunch of static HTML files. With something like PHP,
that's a great thing since now you go from re-evaluating the code on
every page hit (that is, if you run PHP without an opcode cache) to
probably just holding it in the server's filesystem cache, ready to be
returned in as long as it takes for the OS to pull data out of its
filesystem cache.
Or you could just use Emacs. ;-) After all, that's another good
compromise between hand-written code and having a CMS on the server do
it all for you. You could just write a few LISP routines...
--- Mike
_______________________________________________
Ale mailing list
<A HREF="mailto:Ale@ale.org">Ale@ale.org</A>
<A HREF="http://mail.ale.org/mailman/listinfo/ale">http://mail.ale.org/mailman/listinfo/ale</A>
See JOBS, ANNOUNCE and SCHOOLS lists at
<A HREF="http://mail.ale.org/mailman/listinfo">http://mail.ale.org/mailman/listinfo</A>
</PRE>
</BLOCKQUOTE>
<BR>
</BODY>
</HTML>