on 5/23/01 11:19 AM, "Sky Torch" <[EMAIL PROTECTED]> wrote:
> Hello,
>
> if same xyz.vm template is accessed twice, is it going
> to cached somewhere, i.e. the second request doesn't
> need the template to parsed again ?
>
> i guess it depends on service impl of that template
> in Turbine. if so, can someone point out what services
> are doing this, what not?
>
> also, if it does cache, it's using cache service to
> do this ?
There are several levels of caching you need to consider:
Template caching is handled by Velocity. Configure that in TR.props
through the Velocity Service configuration.
Module instance caching (ie: Screens, Actions, Layouts, Pages,
Navigations) is also configured in the TR.props file. Look for
module.cache I belive.
Template path's are also cached. In other words, Turbine does lookups to
find the right template to execute. This lookup is also cached. This is
also controlled in the TR.props file.
-jon
--
If you come from a Perl or PHP background, JSP is a way to take
your pain to new levels. --Anonymous
<http://jakarta.apache.org/velocity/ymtd/ymtd.html>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
