Yesterday, a couple or our engineers noticed that WebMacro is caching
content which has been #include'd when *template* caching is turned on. 
While this could be useful in some situations (where static content
really is static), ours does not happen to be one of them.  ;)

How does Velocity handle this?  IMO, the caching of schmoo should be
configurable through a separate property from template cache.
-- 

Daniel Rall <[EMAIL PROTECTED]>

Reply via email to