Posted by pittendrigh on 10/16/06 19:33

There must be millions of dynamically generated
html pages out there now, built by on-the-fly php code
(and jsp, perl cgi, asp, etc).

Programatic page generation is transparently useful.
But querying a database, negotiatinig lots of if-then-else logic
and echo'ing html code out on port 80 every time a
page is requested has to be a huge waste of resources.

Why not use that logic to print static html instead of dynamic?
The few pages that need to be dynamic (perhaps the results of a
database
query) probably represent only a small fraction of the total
number of pages that are rendered by on the fly code.

Seems to make sense to me. All you need to do is work
the output directories into your code logic somehow,
and do a few one-time-only mkdirs before printing out the static html.

Am I missing something?
Why is it so little open source page generation software acually
works that way?

• Next in forum: using a set of arrays togther and keeping data in sync?
• Prev in forum: Bring some Ruby/Prototype Flavour in your Regular PHP Array
• Thread view: Why not generate static pages instead of dynamic?

[Reply to this message]