Hello everyone! I have a working solution for this now. It uses the store to share locks (objects the threads call wait() and notify() on). It works quite beautifully, for both pipelines and readers. I played around a bit with the eventcache samples for testing (it already had an artificially slowed down generator) and around 60 sequentially opened firefox tabs return the same time after the first request is done :D Same with a reader.
I'm trying to apply the same to trunk now... have to orient myself first though, got a bit confused by the whole mavenation thing.. max > -----Original Message----- > From: Max Pfingsthorn > Sent: Monday, February 06, 2006 12:10 > To: [email protected] > Subject: RE: making pipelines wait for each other > > > > > 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. > > I had a look and the only thing I found was a conversation in > the beginning of 2004 about eventcaching and the CachedSource > [1]. Unico started it back then, but it was about > asynchronously recreating sources instead of making pipelines > wait if another is already recreating the same content. > > I think I will try the approach I outlined before and see > what happens :) > > Bye! > max > > [1] > http://marc.theaimsgroup.com/?l=xml-cocoon-dev&m=107822781408011&w=2 >
