Stephen Howard wrote: > The Caching TT2 does for templates is great. What I'm interested in doing, however, >is to add an additional layer of caching on top of it, which caches the final output >of template + data.
You would be better off simply putting a caching proxy server in front and sending Expires headers. > The problem I have is there's no easy way for an external script that uses the >toolkit to know when any given piece of a cached template is out of date. Finding that out would require parsing the templates to determine dependencies and stat-ing the files on disk. Too slow. I suggest you don't try to determine this, but rather just clear your result cache any time you update templates. > - compile the two to the final format and store it in a finalized form for quick >delivery The final format is HTML, and the proxy server does this for you. You just have to choose expiration times intelligently. Of course this won't work if you absolutely positively can't have any slightly out-of-date pages served from your site, but that isn't the case with most sites. - Perrin _______________________________________________ templates mailing list [EMAIL PROTECTED] http://www.template-toolkit.org/mailman/listinfo/templates
