Mailing-List: contact users-help@cocoon.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@cocoon.apache.org
From: "Carsten Ziegeler" <cziegeler@s-und-n.de>
To: <users@cocoon.apache.org>
Subject: RE: CachingURICoplet versus URICoplet and Refresh
Date: Thu, 19 Aug 2004 15:47:27 +0200
Organization: S&N AG
MIME-Version: 1.0
Thread-Index: AcSFv5d8jnBGkG4BRbWebNjfi9sCkQAMxHvw
In-Reply-To: <1092901086.7000.7.camel@localhost.localdomain>
Message-ID: <OF3713447D.5369B8E9-ONC1256EF5.004BA85A@sundn.de>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain;
	charset="us-ascii"

> 
> 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.

HTH
Carsten


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@cocoon.apache.org
For additional commands, e-mail: users-help@cocoon.apache.org