The question is: shall we adopt the Watchdog interface with a choice of
using either a dual or shared thread implementation? Advantages of the
change have already been presented, and include:
1) Supports both dual-thread and shared-thread implementations.
2) Provides a standalone, reusable service that can be used in
non-Avalon situations. I would suggest that we can donate
the code, so to speak, to Jakarta-Commons. This is a very
useful, and oft-needed, facility.
3) Can easily be unit tested outside of an Avalon container.
The code has already been written to make this change, so there is little
effort to adopt the vote. I don't see any downside to adopting this
interface, and because it allows the choice of either implementation, both
"camps" should be satisfied. Both Harmeet and Peter have told me,
personally, that they appreciate my efforts to mediate the issue. This is
my best proposal.
I don't get a vote (and I am really beginning to regret that), but my
non-vote is +1.
--- Noel
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
