Thanks Martin! If possible can you please give a hint how to use behavior to cache the rendered HTML for a component?
On 24.03.2010, at 10:26, Martin Sachs wrote: > hi, > > we need caching of components, since the construction of huge > hierarchies is not cheap. The rendering ist fast. We cache the rendered > HTML of a hole component via a beheaviour and write them on the next > requests into a Label (unescaped). So instead of creating the complete > hierarchie on every request, we create a much smaller one. But you must > check, that the cachable components are stateless. Also we have JQuery > for client-effects in this components, this would also be cached. > > The performance is much better with that: approx. 10-50 times better: > 100ms with cache (the response time is not much depending on count > of users) > vs > 1500 ms without cache depending how many parallel users. > > > in near feature i will announce the site officially here. > > Martin --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
