Tosh Cooey <[EMAIL PROTECTED]> writes: > After reading some of the things that Randall has suggested I was > thinking about making the "menu" static, but then I have to rebuild > after every change, and also lose a bit of dynamism. > > I'm running a mod_perl environment. > > Is this just a case of; "six of one, one-half dozen of the other" or > is forcing a Template->process call on hapless static HTML, just to > put in a menu, a bit of overkill?
To a first approximation, CPU spent at "build" time is free. You build so few times, compared to the number of times the page is viewed. So unless you *need* minute-by-minute dynamic generation of your site, you win by using a build-time process to produce pages which are then served statically. I've used this on the last couple of sites I've designed, and am liking it *very* much. In both of them I do have a couple of live CGIs for things that really *do* change minute by minute. I also have an automated every-day rebuild, so that scheduled events can be listed only for the current and future days, not letting the past events linger around. -- David Dyer-Bennet, <[EMAIL PROTECTED]>, <www.dd-b.net/dd-b/> RKBA: <noguns-nomoney.com> <www.dd-b.net/carry/> Photos: <dd-b.lighthunters.net> Snapshots: <www.dd-b.net/dd-b/SnapshotAlbum/> Dragaera mailing lists: <dragaera.info/> _______________________________________________ templates mailing list [EMAIL PROTECTED] http://lists.template-toolkit.org/mailman/listinfo/templates
