cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Bruno Dumon <br...@outerthought.org>
Subject Re: CommandManager issues [was Re: Releasing 2.1.1?]
Date Tue, 02 Sep 2003 18:32:37 GMT
On Tue, 2003-09-02 at 19:24, Berin Loritsch wrote:
> Bruno Dumon wrote:
> 
> > 
> > Looking at the code again, I still think that all events from one
> > CommandManager are handled by one thread.
> > 
> > If you look at the code of the AbstractThreadManager:
> > 
> > In the method "register( EventPipeline pipeline )" one PipelineRunner is
> > created to handle events from the given EventPipeline (e.g. the one of
> > the CommandManager).
> > 
> > Then in the run() method the PipelineRunners are executed in parallel by
> > using the PooledExecutor: m_executor.execute( nextRunner );
> 
> The PooledExecutor takes care of initiating and managing the running threads.
> It also takes care of running the tasks in those threads.

D'oh! I looked over the fact that the same PipelineRunner can of course
be run multiple times concurrently, and thus handle commands for the
same CommandManager. Stupid of me :-)

-- 
Bruno Dumon                             http://outerthought.org/
Outerthought - Open Source, Java & XML Competence Support Center
bruno@outerthought.org                          bruno@apache.org


Mime
View raw message