ONJava.com -- The Independent Source for Enterprise Java
oreilly.comSafari Books Online.Conferences.

advertisement

AddThis Social Bookmark Button
Weblog:   one more post about ApacheCon 2003
Subject:   Tapestry / Cache
Date:   2004-01-20 08:41:43
From:   hlship
I may be remembering wrong, but the issue that was brought up wasn't the speed of the cache -- it was that, unlike JSPs, changing a Tapestry specification or template doesn't take effect immediately unless you purge Tapestry's cache.


There's an option to purge the cache after every request, but then the app runs a bit slower (not terrible, but noticibly slower).