|
From: Dejan K. <dej...@nb...> - 2003-07-10 14:45:50
|
Could you commit your code? If that is just new feature that users may or may not use I don't see the reason why it could not become part of standard distribution. Anyway, next (1.1) version is mostly experimental version with a lot of new features. We will try to make them stable in 1.2. Dejan ----- Original Message ----- From: "Leech, Jonathan" <jl...@vi...> To: "'Dejan Krsmanovic'" <dej...@nb...>; "Babeldoc Developer List" <bab...@li...> Sent: Thursday, July 10, 2003 4:00 PM Subject: RE: [Babeldoc-devel] threading and ordering of Router / XpathSplitter Pipeline stages > I put almost all of the functionality in PipelineStage and > PipelineStageFactory. I had to make a few changes to RouterPipelineStage, I > don't think I had to touch XpathSplitterPipelineStage to make it work. Also > assorted, hopefully non-impacting changes elsewhere to make everything > behave nicely with threads. > > If you don't specify any of the new options, it works as it did before. > > -Jonathan > > > -----Original Message----- > From: Dejan Krsmanovic [mailto:dej...@nb...] > Sent: Thursday, July 10, 2003 6:13 AM > To: Babeldoc Developer List > Subject: Re: [Babeldoc-devel] threading and ordering of Router / > XpathSplitter Pipeline stages > > > Are these new pipeline stages or existing stages with new options? Could it > be used with existing configuration? I mean if you don't specify order, > threaded or maxtreads options would everything work as it worked earlier? > > Also, do you think it would be possible to generalize this functionality in > one abstract class and let Router and XpathSplitter (and other classes) to > extend this class. We should identify common functionality for these classes > (something like is done with Writer stages). > > Opinions? > > Dejan > > > ----- Original Message ----- > From: Leech, Jonathan > To: bab...@li... > Sent: Thursday, July 10, 2003 12:01 AM > Subject: [Babeldoc-devel] threading and ordering of Router / XpathSplitter > Pipeline stages > > > I've got it prototyped and working! Thanks Dejan for the idea of adding an > attribute to specify ordering -- I was stuck on the idea of the order coming > from the order in the config file... > > The general idea is to add the attributes 'order', 'threaded', and > 'maxthreads' to any pipeline stages that can create more than one output > document. > > The only thing its missing is the 'maxthreads' idea, I've got it hardcoded > to 5. > > -Jonathan > > Example config of ordered router: > example.stageType=Router > example.nextStage.step1=true > example.nextStage.step2=true > example.nextStage.step3=true > example.order.step1=1 > example.order.step2=2 > example.order.step3=3 > > Example config of parallel router: > example.stageType=Router > example.nextStage.step1=true > example.nextStage.step2=true > example.nextStage.step3=true > example.threaded=true > example.maxthreads=2 > > Example config of parallel XpathSlitter > example.stageType=XpathSplitter > example.nextStage=step1 > example.XPath=//foo/bar > example.threaded=true > example.maxthreads=10 > > > > > ------------------------------------------------------- > This SF.Net email sponsored by: Parasoft > Error proof Web apps, automate testing & more. > Download & eval WebKing and get a free book. > www.parasoft.com/bulletproofapps > _______________________________________________ > Babeldoc-devel mailing list > Bab...@li... > https://lists.sourceforge.net/lists/listinfo/babeldoc-devel |