logging-log4j-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject DO NOT REPLY [Bug 48907] Implement zeroconf support for additional receivers
Date Mon, 15 Mar 2010 07:09:40 GMT
https://issues.apache.org/bugzilla/show_bug.cgi?id=48907

--- Comment #1 from Scott Deboy <sdeboy@iname.com> 2010-03-15 07:09:37 UTC ---
What is needed to implement this feature?
 - Define supported service names (and optionally supported name/value keys)
 - Implement ZeroConf support for all appropriate receivers and appenders
 - Implement auto-creation of a receiver configuration in Chainsaw based on a
discovered service

Proof of concept implementation
I've implemented a proof of concept which adds support for ZeroConf to the
MulticastAppender & receiver, SocketAppender & receiver, SocketHubAppender &
receiver (sockethubappender already has support via a subclass, but that won't
be needed going forward), UDPAppender and receiver, and XMLSocketReceiver.

Each of these appenders and receivers now contains a new member:
advertiseViaMulticastDNS

When activateOptions is called, if the value of this property is 'true', a new
class in the core log4j tree (ZeroConfSupport) is instantiated and the appender
or receiver 'service' is registered via JmDNS.  The service is unregistered
when the appender or receiver is closed/shut down.

Service names need to be defined and documented in order to support
advertisement of appenders as well as auto-configuration of receivers in
Chainsaw based on these service names.  

This will allow other logging frameworks to register appender configurations
and have Chainsaw automatically construct an appropriate receiver
configuration.  

It will also allow those applications to discover receivers (possibly defined
in Chainsaw) which they can send their events to.

Thoughts?

-- 
Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.

---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-dev-unsubscribe@logging.apache.org
For additional commands, e-mail: log4j-dev-help@logging.apache.org


Mime
View raw message