You will run into problems when the remote server does not respond in normal times. We experienced lots of troubles for rss feeds. Better to define a cron jobs, writing every X minutes the file to file system, only if the file gets parsed correctly. This assures your front end not being dependant on a remote server..
> -----Original Message----- > From: news [mailto:[EMAIL PROTECTED] Behalf Of Jorg Heymans > Posted At: maandag 3 oktober 2005 9:29 > Posted To: Cocoon User List > Conversation: Re: Can caching be forced? > Subject: Re: Can caching be forced? > > > > Rob Oxspring wrote: > > Hi, > > > > I have a match setup to pull data from a remote server for later > > transformation. The data from the remote server doesn't > appear to have > > accurate last modified or useful expiry information but I'd like to > > minimize calls to the remote server all the same. Is it possible to > > force the remote data to be cached for some fixed period and thereby > > only issue requests to the remote server at some minimum > rate (e.g. 1 > > request per minute). > > > > see [1] > > <map:pipeline> > <map:parameter name="expires" value="access plus 1 minutes"/> > ... > </map:pipeline> > > > HTH > Jorg > > [1] http://cocoon.apache.org/2.1/userdocs/concepts/caching.html > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
