I don't get your comment. Maybe I did not make myself clear. Watchdogs will not be deriving from the Configurator interface. They are clients of the Configurator interface. You specify the Configurator class to use, the Watchdog creates and instance of that Configurator and then calls the doConfigure method on that instance to reconfigure the log4j environment.
Ok, good.
My point is that for some configuration sources, only having a version of doConfigurator that takes a URL is not sufficient. My example was with Socket, but another example might be JMS.
Well, I think JMS is actually a counter example because if I am not mistaken you can't view a JMS channel as an InputStream. Following your line of thought we'd need to change the Configurator interface to support JMS channels.
Coming back to the socket example, how do you see the interaction between the socket and the watchdog? Will the socket be pushing its data?
Does that make sense?
-Mark
-- Ceki G�lc�
The complete log4j manual: http://qos.ch/log4j/
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
