Each *.vm file is cached individually. When the resource loader goes to
retrieve a template (whether the master template or one loaded with #parse)
it first checks the cache.
WILL
On 5/15/07, Erron Austin <[EMAIL PROTECTED]> wrote:
Hi,
I am relatively new to Velocity and I have a couple of questions I hope
someone can help me with.
1) Is there a way for me to determine which items are actually being
cached?
2) In the following scenarios, what type of caching could expect?
a) Using the request Uri, I am parsing the string to pull in the
desired template. For example, /page1/page2 would pull in page1_page2.vm.
In
the this page, would be the following code:
#parse(content/header.vm)
#parse(content/content.vm)
#parse(content/footer.vm)
Would the entire generated page1_page2.vm be cached?
b) Using the request Uri, I am parsing the string to pull in the
desired
template. For example, /page1/page2 would pull in page1.vm. In the this
page, would be the following code: #parse(content/header.vm)
#parse(content/$selectedpage)
#parse(content/footer.vm)
If the entire site was built in the manner, what kind of
performance/caching could I expect?
Thanks in advance for your help!
--
Forio Business Simulations
Will Glass-Husain
[EMAIL PROTECTED]
www.forio.com
