This provider includes full-featured DNS client as part of its functionality and has rather complex logic. It tries to establish big number of networks connections and highly depends on network conditions. In the case of perfomance degradation it is very usefull for system admins to understand the provider's activity. If the provider hangs while connecting to some unreachable server it is important that the name of such server can be extracted from the log and added to the server's black list. And so on. In other words, DNS provider needs to log no less than any other complex network application.
2006/5/30, Geir Magnusson Jr <[EMAIL PROTECTED]>:
I agree with you. Why does it need to log? geir Tim Ellison wrote: > I've just imported the HARMONY-256 contribution of a DNS provider for > JNDI into our repository. That provider introduces a new dependency > between JNDI and LOGGING that we didn't have before. > > IIRC we agreed that we would not scatter logging calls throughout our > implementation code, so unless I hear an objection I'll start to unpick > that dependency and make JNDI independent of LOGGING. > > Regards, > Tim
-- Alexei Zakharov, Intel Middleware Product Division --------------------------------------------------------------------- Terms of use : http://incubator.apache.org/harmony/mailing.html To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
