Return-Path: Delivered-To: apmail-xml-cocoon-users-archive@xml.apache.org Received: (qmail 95127 invoked by uid 500); 27 Feb 2003 16:55:36 -0000 Mailing-List: contact cocoon-users-help@xml.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: list-post: Reply-To: cocoon-users@xml.apache.org Delivered-To: mailing list cocoon-users@xml.apache.org Received: (qmail 95065 invoked from network); 27 Feb 2003 16:55:35 -0000 Received: from mta6.snfc21.pbi.net (206.13.28.240) by daedalus.apache.org with SMTP; 27 Feb 2003 16:55:35 -0000 Received: from stanford.edu ([63.202.83.6]) by mta6.snfc21.pbi.net (iPlanet Messaging Server 5.1 HotFix 1.6 (built Oct 18 2002)) with ESMTP id <0HAZ00KZK8CQ5G@mta6.snfc21.pbi.net> for cocoon-users@xml.apache.org; Thu, 27 Feb 2003 08:55:38 -0800 (PST) Date: Thu, 27 Feb 2003 08:55:38 -0500 From: Charles Yates Subject: Re: caching In-reply-to: To: cocoon-users@xml.apache.org Message-id: <3E5E18DA.8080401@stanford.edu> MIME-version: 1.0 Content-type: text/plain; charset=ISO-8859-1; format=flowed Content-transfer-encoding: 8BIT X-Accept-Language: en-us, en User-Agent: Mozilla/5.0 (X11; U; Linux ppc; en-US; rv:1.3b) Gecko/20030207 References: X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N I am curently testing a 'CacheableSource' and 'CacheableSourceFactory' that does these things. Its not ready for prime time yet but it does do the things mentioned here. Used like this: cache://http://www.unreliableserver.com/news.rdf cache://cocoon://resource/that/takes/a/long/time It uses DeltaTimeCacheValidity. If the validity has expired, it returns the resouce from the cache and updates it in another thread. I'll report back when its ready. Charles Carsten Ziegeler wrote: > > >>-----Original Message----- >>From: Reinhard P�tz [mailto:reinhard_poetz@gmx.net] >>Sent: Thursday, February 27, 2003 12:39 PM >>To: cocoon-users@xml.apache.org >>Subject: RE: caching >> >> >> >> >>>From: Carsten Ziegeler [mailto:cziegeler@s-und-n.de] >>>Reinhard P�tz wrote: >>> >>> >>>>>>Do you know whether there is some mechanism to get the old >>>>>> >>>>>> >>>>>(=expired) >>>>> >>>>> >>>>>>content if the external source is not available after it >>>>>> >>>>>> >>expired? >> >> >>>>>No, it's not possible. >>>>> >>>>> >>>>At which 'level' would you solve that problem? Would you write a >>>>special generator? >>>> >>>> >>>> >>>Yes, exactly. >>> >>>But I'm not sure if this is a good solution. If the external >>>source is not available, you usually get a timeout (4 or 5 >>>minutes?). So, you have to wait for this timeout and then >>>serve from the cache; this time is too long for the casual user. >>> >>>I would suggest that you always serve from the cache even if >>>the content has expired. If it has expired you will the cache >>>in the background. This can be done in a special generator as well. >>> >>> >>Am I right you would write a background component that tries to refresh >>all expired content of the cache and until it is updated the 'old' >>version could be used. >> >> >Yes. > > > >>Would this fit in the already existing "pipeline-expires" and >>"pipeline-caching" concepts? >> >> >> >This would be two different parts, so the >caching algorithm works as always and your generator does his work. >Of course, your generator can be still cacheable and used by the >caching pipeline. > >Carsten > > >--------------------------------------------------------------------- >To unsubscribe, e-mail: cocoon-users-unsubscribe@xml.apache.org >For additional commands, e-mail: cocoon-users-help@xml.apache.org > > > > --------------------------------------------------------------------- To unsubscribe, e-mail: cocoon-users-unsubscribe@xml.apache.org For additional commands, e-mail: cocoon-users-help@xml.apache.org