This talk of caching reminded me of something.

IIRC, currently any template passed as a scalar reference or file
handle is not cached -- there's no associated template name to use as
the key to the cache.

Seems like there should be a way to specify a key to use for caching
in this case.  Perhaps an addition to the %options param to process() in
TT2.  Not sure about TT3.


-- 
Bill Moseley
[EMAIL PROTECTED]


_______________________________________________
templates mailing list
[email protected]
http://lists.template-toolkit.org/mailman/listinfo/templates

Reply via email to