Sam Tregar wrote: > > You say it will check whether the template has changed and therefore needs > > to be recompiled. Does that include noticing if any included templates > > have been modified? I guess that question is based on my assumption that > > you're doing as you did before and that the included template is being > > inlined into the includer... > > Hmmmmm. No, not just yet. I'll put that in the CAVEATS. The problem is > that I don't want to have to parse the template file to figure out if I > can use the precompiled version... That would require loading > HTML::Template itself which is something I'm trying to avoid when not > compiling. I'll think about this more and maybe a good solution will > occur to me.
It may be possible to cache the modification-dates of the templates at compile time, and just check againt file-size and mtime. If a file has been modified, it might be wise to fork a backgound process, which compiles the template, and still serves the old template until the new one is compiled (and moved over the old comp. template) That way a client suffers only the first time-ever from compilation time. If the permissions for writing are not met, the templates should be compiled by a seperate action/script, so the clients do not suffer from the compilation penalty Just my 0.02 EUR +rl ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Roland Lammel fax: +431 60501 3405 Customer Support / TAS phone: +431 60501 3456 mailto:[EMAIL PROTECTED] mobile: +43664 628 3456 Austria Telecommunication, Triesterstr. 70, 1102 Vienna ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ "Enjoy your job, make lots of money, work within the law." Choose any two... --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
