Hi,
you can cache fragments of HTML (if it has no generated html-ids) with a
Behaviour. Look at XlstBehaviour. We have done it that way. But the
bottlenekk is always the Database, not the rendering of small components. By
the way, with such snipplet-caching you can improve the performance max
any hint that can help to apply caching on the html output of a panel?
the panel is dynamic in nature, no ajax, i.e. stateless by itself, and
is unique per url but needs some time to generate
so i want to cache the html output of this panel
This topic has been covered many times here on the list. The result
is that you almost never really need to cache the generated HTML, but
rather the loading of the backing model. Are you really sure that you
need to cache the generated HTML?
--
Jeremy Thomerson
http://www.wickettraining.com
we have tried the best to cache the backing model (or data)
and we are always looking how to push our performance to a limit
it seems we are hitting the limit now,
instead we go to refactor/revamp a lot,
we want to see if we can do anything on wicket such as caching the generated
html that can
If you've done profiling that shows where the Wicket markup generation
is the slow part of your page rendering, we would benefit from seeing
it so that we could see if there was anything that could be improved.
--
Jeremy Thomerson
http://www.wickettraining.com
On Thu, May 21, 2009 at 7:44 PM,
