https://issues.apache.org/bugzilla/show_bug.cgi?id=48907

--- Comment #3 from Scott Deboy <[email protected]> 2010-03-16 04:10:35 UTC ---
After thinking about this a bit, here's a proposal for a service name
convention supporting most of the network-based appenders and receivers we
provide.

Other logging frameworks can conform to this convention in order to have log4j
discover their services, and they can use this convention to discover
log4j-advertised services).  

If, in the future, we want to advertise other appenders (like FileAppenders or
FileReceivers), we will need to expand on this convention.

Support for existing ZeroConfSocketHubAppender deployments:
log4j._tcp.local.

Proposed service name convention:
log4j_[xml/obj]_[mcast/udp/tcpaccept/tcpconnect]_[appender/receiver].local.

We could also support service-defined encoders for xml-based appenders via an
'encoder' key, with the value being the fully qualified decoder class name.

xml: events are sent as xml fragments
obj: events are sent as serialized java objects

mcast: multicast UDP
udp: unicast UDP
tcpaccept: tcp serversocket (accepting incoming connections)
tcpconnect: tcp socket (connect to a remote server socket)

appender: advertised service sends events to receivers
receiver: advertised service receives events from appenders

multicastappender:
_log4j_xml_mcast_appender.local.

multicastreceiver:
_log4j_xml_mcast_receiver.local.

udpappender:
_log4j_xml_udp_appender.local.

udpreceiver:
_log4j_xml_udp_receiver.local.

non-log4j xml socketappender:
_log4j_xml_tcpconnect_appender.local.

xmlsocketreceiver:
_log4j_xml_tcpaccept_receiver.local.

socketappender:
_log4j_obj_tcpconnect_appender.local.

socketreceiver:
_log4j_obj_tcpaccept_receiver.local.

sockethubappender:
_log4j_obj_tcpaccept_appender.local.

sockethubreceiver:
_log4j_obj_tcpconnect_receiver.local.

-- 
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: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to