RE: [Babeldoc-devel] threading

[Leech, J. <jl...@vi...>]

I agree.  If you consider it a threading preference, you can have the
pipeline configuration basically saying "I would prefer you do these N
stages all at once", but whether they really happen in parallel is up to
whether you're allowed threads at all, whether there's any threads available
in a pool, etc. etc.  What I really would want is to be able to configure
different parts of the pipeline to operate in serial / parallel; e.g. for my
application I need to route a document down two different paths, which I
would like to do in parallel.  But for one of the paths, I will be breaking
the document up further into parts, and according to our partner, can only
send one part at a time.  So I have to be able to specify serial there.
What are your thoughts on consolidating various XML bits back into a single
document, once I have split it up and retrieved data from various sources?
I am thinking along the lines of writing all the data to a database and then
querying for it at the end.  It seems like that strategy would be more
compatible with replaying steps than others I have thought of.

-Jonathan

-----Original Message-----
From: Bruce McDonald [mailto:br...@mc...]
Sent: Monday, June 30, 2003 4:31 PM
To: Leech, Jonathan; bab...@li...
Subject: Re: [Babeldoc-devel] threading


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