On 2005-01-05 10:07 AM, Perrin Harkins wrote: > On Wed, 2005-01-05 at 12:18 -0500, Larry Leszczynski wrote: > > >> Is there any way to take advantage of the cache in a non-persistent e.g. > >> non-webserver) environment? Maybe along the lines of serializing the > >> template object and reading it back later? > > No, but the COMPILE_DIR option means that at least the "compile to perl" > step will be skipped. If there was a way to store compiled perl code > and load it faster, it would be used in all kinds of modules. > > - Perrin
--------------------------------- I have another question about caching in this sort of environment:
I would like to be able to indicate for a particular run of process(): a) do NOT use the compilation cached in the COMPILE_DIR b) but DO store the results of this run into the COMPILE_DIR
The only thing I can see that relates to this at all is the COMPILE_DIR option but that doesn't do it at all.
Perhaps this boils down to supporting an explicit cache-purge for a particular file.
Thoughts?
-Len
_______________________________________________ templates mailing list [email protected] http://lists.template-toolkit.org/mailman/listinfo/templates
