So what you need then is a templating system which caches the generated content from the templates and then when asked for it again later, it checks if the template has been changed, and if it hasn't (so the content generated will be the same if executed), answer the browser with a "Content not changed" instead of sending the content.

Looks like you might need Template::Plugin::Cache:

http://search.cpan.org/~perrin/Template-Plugin-Cache-0.13/Cache.pm

Specially interesting the "Any gotchas..." section of the docs :-)

Regards
J.


Jorge González Villalonga
Director Técnico


DAIKON Integración y Desarrollo S.L.
Telf: (+34) 91 188 08 28
Fax: (+34) 91 632 65 42
www.daikon.es

El 01/03/11 10:23, John M. Dlugosz escribió:
 Say I want to use TT in the .css, so (for example) I can name my colors and other repeated content easily.

I'm assuming that I can define a Path of some kind on a rule to serve those.  Any recipes to share?
More critically, I want the browser to know that it doesn't have to keep re-fetching it on every view of every page.  How would I manage that?

_______________________________________________
List: Catalyst@lists.scsys.co.uk
Listinfo: http://lists.scsys.co.uk/cgi-bin/mailman/listinfo/catalyst
Searchable archive: http://www.mail-archive.com/catalyst@lists.scsys.co.uk/
Dev site: http://dev.catalyst.perl.org/
_______________________________________________
List: Catalyst@lists.scsys.co.uk
Listinfo: http://lists.scsys.co.uk/cgi-bin/mailman/listinfo/catalyst
Searchable archive: http://www.mail-archive.com/catalyst@lists.scsys.co.uk/
Dev site: http://dev.catalyst.perl.org/

Reply via email to