Craig R. McClanahan wrote on 8/16/01 1:06 pm:
>
>
>On Thu, 16 Aug 2001,
>Morgan Delagrange wrote:
>
>>
>> --- "Craig R. McClanahan"
><[EMAIL PROTECTED]>
>wrote:
>> >
>> >
>> > On Thu, 16 Aug 2001,
>Rodney Waldhoff wrote:
>> >
>> > >
>> > > I agree that for the
>specific case you cite the
>> > API contract is sufficient.
>> > > But allow me to provide
>some concrete examples of
>> > where logging (and not
>> > > debugging) is more
>useful.
>> > > [snipped the example -
>see the complete post for
>> > details]
>> >
>> > At the risk of starting a
>whole new discussion,
>> > would having event
>> > listeners in the Pool and
>DBCP APIs reduce the need
>> > for logging for this
>> > type of thing? (As
>you've heard me say, I don't
>> > like embedding logging
>> > code in components, so
>I'm looking for excuses not
>> > to :-).
>> >
>> > Craig
>> >
>>
>> But then you have to
>configure the event
>listeners, etc. etc. etc. I'd
>prefer to leverage a logging
>API as a single point of
>configuration.
>>
>
>That makes sense.
>
>But that's not to say an
>event model might not be
>useful as well -- for example,
>if you want your app to take
>some action when those
>events have occurred (and
>not just be able to read
>about them in a log later).
>
>Craig
Yup that's true.
_________________________________________________________
Do You Yahoo!?
Get your free @yahoo.com address at http://mail.yahoo.com
