Brian Cassidy [EMAIL PROTECTED] wrote:
Mark,
-Original Message-
If there's nothing dynamic, why not write out a bunch of HTML files
ahead of time, and dispense with CGI::App altogether?
Good point, however, part of my goal is to allow all of the HTML-ized Gedcom
records to be auto-updated when the Gedcom data file is updated (thus
eliminating the need of a generator script). Why? ... I have no idea --
why not? :)
I addressed the same kind of problem in Cascade by having a write
static pages run mode.
After I'd made several updates, I would run that function. This is how
most of http://www.skatepark.org/ is produced.
Some pages remain dynamic-- search results and pages where users can
comment.
I like the transparency of your caching approach, though. It seems like
it would work well when other, non-technical people were making the
changes that caused updates to be made. They would need to be trained to
make sure they published their changes. (Or perhaps a cron script
could do that...).
Mark
-
Web Archive: http://www.mail-archive.com/[EMAIL PROTECTED]/
http://marc.theaimsgroup.com/?l=cgiappr=1w=2
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
