> -----Original Message----- > From: Carsten Ziegeler [mailto:[EMAIL PROTECTED] > Sent: Monday, February 06, 2006 11:35 > To: [email protected] > Subject: Re: making pipelines wait for each other > > Max Pfingsthorn wrote: > > Hello! > > ... > > > > WDYT? Would that solve it? Is there a better way? > > > I think this topic has been discussed several times, so you might want > to search through the archives to see what others did say about it. > > We usually solve this problem by pre-caching, so before the first real > user can invoke the pipeline, we already invoked it (using cron etc.) > and therefore the content is always cached.
Yes, that is one solution, but we have dynamic content, and a vast range of possible http requests, so we can't precompute everything. Additionally, when content changes while cocoon is running, it is still possible to get this effect while the background task refreshes the cache... Unless we do some double buffering, i.e. keep the previous cachedresponse valid while we recreate the content. I'll have another look through the archive before I take some steps to solve this. max
