Exactly. Will have that done and checked in tonight. Generally, stuff that is #included() are not templates, so the handling will be different. The stuff will be cached in that it won't be read off the disk every time, but it will check file modification times or something to ensure that any changes to the included material are always immediately #included().
geir
-----Original Message-----
From: Daniel L. Rall [SMTP:[EMAIL PROTECTED]]
Sent: Wednesday, November 15, 2000 1:32 PM
To: Velocity Development List
Subject: #include'd schmoo cache
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]>
