Don't share component instances across requests / especially sessions. Don't prematurely optimize.
Cache your model and test the rendering. If it really is taking too long, figure out why and worry about it then. -- Jeremy Thomerson http://www.wickettraining.com On Fri, Mar 27, 2009 at 1:12 PM, Martin Grotzke < [email protected]> wrote: > Hi, > > I also thought about s.th. like this because we'll have very complex > component graphs that have to be composed dynamically based on the > language of the user and ~3 other things. I thought about caching > complete component instances, but didn't come so far that I thought > about how this could be integrated into wicket - perhaps dead simple via > some > _cacheService.getReallyComplexComponentCached( "complexComponent", > userInfo ) > > I don't know how cheap exactly rendering of our complex component > structure will be, but if this would take more than say 10 millis we > would also try to cache already rendered markup. > > Cheers, > Martin > > > On Fri, 2009-03-27 at 16:49 +0100, Daniel Frisk wrote: > > I have a situation where I have some panels which I want to render say > > at most once a minute and during that period they should be "static". > > I tried a few approches which hasn't really worked out for me so I > > wanted to know if somebody has created such a thing or how this could > > be done. Ideas are also welcome... > > > > // Daniel Frisk > > jalbum.net > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [email protected] > > For additional commands, e-mail: [email protected] > > >
