ok solved (don't know why I didn't see this earlier ;-) simply tested in template if cached html existed. if false --> render component if true --> use OutputRaw to output cached html of component.
cheers, Britske Britske wrote: > > currently I'm working on a page with a lot of components. > > part of these components are lists with contents related to the visitor > viewing the page (i.e: last viewed products, product in wishlist) but most > of these components display lists which are related to context of the page > only (and are thus visitor-independent.) > > Because of: > a. rather big processing time of these components > b. pretty static nature of the visitor-independent components (changes > once a night) > c. limited nr of possible contexts > > it seems a good idea to wrap all visitor-independent components in a new > 'container component' of which I would like to cache the outputted html. > > Has anybody done something like this before, and if yes how? Are there any > 'tapestry-ways' to go about it? > If not, in the basis I just need to know how to fetch the output of a > component as html, so I can insert it in memcached using the pagename+ > context as key. > > Thanks for you help, > Britske > -- View this message in context: http://www.nabble.com/t5%3A-strategy-for-caching-html-output-of-component-tp23394162p23397603.html Sent from the Tapestry - User mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
