cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Henrik Gustafsson" <>
Subject Re: Implementation of the Continuations checker
Date Fri, 29 Oct 2004 10:11:03 GMT
Maybe it is not important in this case but I would like to raise 
a warning for the java.util.Timer and java.util.TimerTask. 
I had some serious problems with this in a high performance 
server implementation since you loose control of the threading. 
I guess this is the reason why they are introducing the 
concurrent package with timer support in jdk 1.5

/Henrik Gustafsson

----- Original Message ----- 
From: "Sylvain Wallez" <>
To: <>
Sent: Friday, October 29, 2004 11:26 AM
Subject: Re: Implementation of the Continuations checker

> Carsten Ziegeler wrote:
>>The current implementation of our continuations manager uses
>>the excalibur event package for the background checker that
>>checks for expired continuations.
>>Now, this approach has the problem, that excalibur event is
>>deprecated. In addition we aren't using it somewhere else,
>>so it would be great if we could remove this dependency.
>>Yesterday, I wrote a simple replacement which I checked into 2.2:
>>a simple background thread is initialized that sleeps for a 
>>configured period of time, checks the continuations, sleeps etc.
>>Now, this solution should work.
>>The question is now, should I port this to 2.1.x as well? Are there
>>better solutions?
> java.util.TimerTask?
> Sylvain
> -- 
> Sylvain Wallez                                  Anyware Technologies
> { XML, Java, Cocoon, OpenSource }*{ Training, Consulting, Projects }

View raw message