Has anybody implemented page caching for Wicket? If possible, I'd
like to
store the markup of a page in ehcache so that subsequent requests can be
served without invoking the rendering mechanism of the framework at all.
Being a wicket newbie, I am not sure whether such an approach might
at all
be compatible with the framework? I understand that Wicket serializes
pages
at some points, so if a page where handled from the page cache (without
informing Wicket), this might be a problem. Any experiences?
Background: I am porting a Tapestry 4 application to Wicket. In our old
application, we use two layers of caching, one at the application level
and one at the web presentation level. The former already exists and can
be reused without problems. The latter cache stores the generated markup
in ehcache and returns it -- without invoking the Tapestry rendering at
all -- on subsequent requests. (The cache activates only when the user
is not logged in, to make sure that the page content is static.)
Provided Wicket is fast enough, we can of course go without the page
cache
but I have not enough experience with Wicket. In Tapestry, we saw quite
a difference in timing (20ms vs 300ms) for larger pages, but that might
be because we used lots of OGNL expressions in our Tapestry markup
(which
is not Tapestry's but our fault, of course).
Many thanks for hints,
Kaspar
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
