cocoon-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Philippe Guillard <>
Subject RE: CachingURICoplet versus URICoplet and Refresh
Date Fri, 20 Aug 2004 09:41:27 GMT
Thanks Carsten,

I profit you are here for a last question, same subject :

In CachingURI i develop coplets without trouble outside portal and know
my links will be transfomed to events.

In URI coplets i find the only solution is to set copletData/attributes
via cl:link or bookmark and use them in generator/transformer etc... Is
this right or there is some other way?



On Thu, 2004-08-19 at 21:47, Carsten Ziegeler wrote:
> > 
> > Question1:
> > I'd like to know if there is another way to refresh 
> > CachingURICoplet than setting bookmarks or cl:link evrywhere, 
> > or even invalidate the cache. Maybe for that purpose i should 
> > use URICoplets ?
> > 
> You can invalidate the cache "manually" from within flow or
> any component using Java.
> > Question2:
> > Until now i adopted this rule : if i need CForms + Flow 
> > (continuation) or internal links that need to be transformed 
> > by portal-html-eventlink transformer i use CachingURI 
> > Coplets, otherwise i use URI Coplets. Is this a right idea ?
> > 
> This depends, but basically: yes. The caching uri coplet is a
> must for cforms + flow (or for just flow). It caches the content
> (or the view) of the coplet until an action is performed in this
> coplet. 
> The uri coplet does not cache, so each time the page is displayed
> the content is fetched from the source again. If this is a heavy
> operation it might be wise to cache this content as well either
> using the cachinguricoplet or using a usual cocoon pipeline that
> uses the cocoon caching mechanism.
> Carsten
> ---------------------------------------------------------------------
> To unsubscribe, e-mail:
> For additional commands, e-mail:

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message