Harmeet,
The Avalon Scheduler doesn't leak. It gets flooded. Big difference.
FetchPOP doesn't cause flooding.
In any event, my point is that if anyone is going to be able to use your
Scheduler instead of the default from Avalon, that you'll have to fix that
bug.
--- Noel
-----Original Message-----
From: Harmeet Bedi [mailto:harmeet@;kodemuse.com]
Sent: Friday, October 25, 2002 22:48
To: James Developers List
Subject: Re: Commiting recent changes (was: Code change the Apache way)
----- Original Message -----
From: "Noel J. Bergman" <[EMAIL PROTECTED]>
> Harmeet, since FetchPOP does use the Scheduler in the way it is designed
> to work, I think you do need to address the problem I have mentioned
> about it not working properly when inserting a time earlier than the
> current head of the list. Until that is resolved, I don't think that
> it can replace the general Scheduler Block.
If we are going to live with the scheduler, it may be a good idea to have
the bug fixed version that was posted rather than the current one with
memory leak.
Harmeet
--
To unsubscribe, e-mail: <mailto:james-dev-unsubscribe@;jakarta.apache.org>
For additional commands, e-mail: <mailto:james-dev-help@;jakarta.apache.org>
