On Wed, 5 Jan 2005, Perrin Harkins wrote: > I can't stress enough that this really makes a difference. By creating > a new object every time, you are breaking TT's caching system. It has > to compile the perl code for each template used on every single request. > It's almost as bad as the difference between CGI and PersistentPerl.
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? Just curious, Larry Leszczynski _______________________________________________ templates mailing list templates@template-toolkit.org http://lists.template-toolkit.org/mailman/listinfo/templates
