[Catalyst] template toolkit caching

John Goulah jgoulah at gmail.com
Thu May 31 19:42:57 GMT 2007


On 5/31/07, Perrin Harkins <perrin at elem.com> wrote:
>
> Hi guys,
>
> > I believe Template::Plugin::Cache will do what you want. Perrin (the
> author) has
> > a patch from me that lets you pass in the Cache object from Catalyst and
> use
> > that, so any supported backend is available. If you bug him, I'll bet
> he'll get
> > a new version up on CPAN. ;)
>
> Yes, sorry I haven't put that up yet, Peter.  Coming soon.
>
> John, are you trying to change the way that TT stores the compiled
> templates?  My module doesn't affect that.  It offers a way to cache
> the generated output from templates.
>
> To change how compiled templates are stored, you would override (I
> think) Template::Provider and change the Template configuration to use
> your version.  In my opinion, this wouldn't really be worth the effort
> though, since the compiled code is stored in memory after the first
> hit in each process.
>
> - Perrin



Thanks for the feedback.  Yes I was looking more for a way to cache the
compiled templates in memcache.  The reason being with many servers the
compiled template could  be shared amongst the servers so that its only
compiled once.  Maybe that doesn't buy much, but it probably depends on how
many templates and servers are in the mix-

Thanks,
John
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.scsys.co.uk/pipermail/catalyst/attachments/20070531/70efd=
c05/attachment.htm


More information about the Catalyst mailing list