|
From: Bruce M. <br...@mc...> - 2003-06-30 22:30:45
|
Whoa!!! Sorry, I misunderstood (I just wrote a hammer - and now all I see is nails) no, this is not something that can be just done in an ad-hoc fashion. The running of stages in a pipeline must be switchable between multi- and single-threaded. This is because certain environments do not tolerate application spawned threads (J2EE). What I think can be done here is introducing a "ThreadingPolicy" object that can be configured for each environment. So usually its MultiThreaded (using a thread pool) but it can also operate synchronously. What do you think? regards, B ruce. On Monday 30 June 2003 06:23 pm, Bruce McDonald wrote: > Jonathan, > > Ok, I have just implemented a feederfactory which should make this kind of > thing easy. So just submit the document using the asynchronous feeder > instead of the synchronous feeder and you are done. > > regards, > Bruce. > > On Monday 30 June 2003 01:19 pm, Leech, Jonathan wrote: > > I'm using a Router pipeline stage to send the same document down multiple > > paths... Is there currently any way to make these pipeline stages get > > processed in parallel instead of sequentially? If not, maybe something > > along the lines of the <parallel> and <sequential> tags in ant would > > work... > > > > Sincerely, > > Jonathan Leech > > Senior Software Engineer > > Virtela Communications, Inc. > > ------------------------------------------------------- > This SF.Net email sponsored by: Free pre-built ASP.NET sites including > Data Reports, E-commerce, Portals, and Forums are available now. > Download today and enter to win an XBOX or Visual Studio .NET. > http://aspnet.click-url.com/go/psa00100006ave/direct;at.asp_061203_01/01 > _______________________________________________ > Babeldoc-devel mailing list > Bab...@li... > https://lists.sourceforge.net/lists/listinfo/babeldoc-devel |