You are viewing a plain text version of this content. The canonical link for it is here.
Posted to log4j-dev@logging.apache.org by Paul Smith <Pa...@lawlex.com.au> on 2003/04/22 02:56:33 UTC
WatchDog & Plugins
Hi Mark,
Just reviewing the whole plugins arena, and wondering if you could
articulate a little on your current thoughts for the design of a flexibile
WatchDog/Cat mechanism (you should see my cat...)
cheers,
_________________________
Paul Smith
Lawlex Compliance Solutions
phone: +61 3 9278 1511
email: paul.smith@lawlex.com.au
---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: log4j-dev-help@jakarta.apache.org
RE: WatchDog & Plugins
Posted by Ceki Gülcü <ce...@qos.ch>.
Hi Mark,
What is the state of the work on plug-ins and watchdogs? A short
description would be sufficient. I'd like to help if I can.
At 07:41 PM 4/21/2003 -0700, mwomack@apache.org wrote:
>Paul,
>
>Well...there has been a lot of discussion about this topic previously ("...I
>remember when I joined the log4j email list and I had to wade through that
>watchdog email thread, up hill, both ways..."). And it was pre-plugins.
>
>http://marc.theaimsgroup.com/?t=102264999800003&r=1&w=2
>
>http://marc.theaimsgroup.com/?t=102282119300003&r=1&w=2
>
>My thinking right now is to create a base Watchdog class based on Plugin,
>similar to how it is done right now for Receiver. Then, build on top of
>that base class in a fashion similar to the what is discussed above. The
>end result will be a set of classes that support watching a file, an http
>url, or a socket. And hopefully some useful base classes that can be used
>by developers to develop versions to watch other sources as well.
>
>I think I am going to start looking at it tonight (almost over a year after
>I suggested it...). So, some discussion of it will be good.
>
>-Mark
--
Ceki Gülcü
For log4j documentation consider "The complete log4j manual"
ISBN: 2970036908 http://www.qos.ch/shop/products/clm_t.jsp
---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-dev-unsubscribe@logging.apache.org
For additional commands, e-mail: log4j-dev-help@logging.apache.org
RE: WatchDog & Plugins
Posted by mw...@apache.org.
Paul,
Well...there has been a lot of discussion about this topic previously ("...I
remember when I joined the log4j email list and I had to wade through that
watchdog email thread, up hill, both ways..."). And it was pre-plugins.
http://marc.theaimsgroup.com/?t=102264999800003&r=1&w=2
http://marc.theaimsgroup.com/?t=102282119300003&r=1&w=2
My thinking right now is to create a base Watchdog class based on Plugin,
similar to how it is done right now for Receiver. Then, build on top of
that base class in a fashion similar to the what is discussed above. The
end result will be a set of classes that support watching a file, an http
url, or a socket. And hopefully some useful base classes that can be used
by developers to develop versions to watch other sources as well.
I think I am going to start looking at it tonight (almost over a year after
I suggested it...). So, some discussion of it will be good.
-Mark
> -----Original Message-----
> From: Paul Smith [mailto:Paul.Smith@lawlex.com.au]
> Sent: Monday, April 21, 2003 5:57 PM
> To: Log4j-Dev (E-mail)
> Subject: WatchDog & Plugins
>
>
> Hi Mark,
>
> Just reviewing the whole plugins arena, and wondering if you could
> articulate a little on your current thoughts for the design of a flexibile
> WatchDog/Cat mechanism (you should see my cat...)
>
> cheers,
> _________________________
> Paul Smith
> Lawlex Compliance Solutions
> phone: +61 3 9278 1511
> email: paul.smith@lawlex.com.au
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: log4j-dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: log4j-dev-help@jakarta.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: log4j-dev-help@jakarta.apache.org