https://issues.apache.org/bugzilla/show_bug.cgi?id=48907
Summary: Implement zeroconf support for additional receivers
Product: Log4j
Version: unspecified
Platform: All
OS/Version: All
Status: NEW
Severity: enhancement
Priority: P2
Component: Other
AssignedTo: [email protected]
ReportedBy: [email protected]
Include ZeroConf support for additional receivers (UDPReceiver,
MulticastReceiver, XMLSocketReceiver).
Currently, _log4j._tcp.local. is the service name associated with a
ZeroConfSocketHubAppender (a SocketHubReceiver initiates a TCP connection to
the appender using port and host address information). This should probably be
left as-is to support existing deployments.
Two possible implementation choices:
1. use _log4j._tcp.local, _log4j._udp.local. and _log4j._multicast.local.
service names and require specific properties which will be used to construct
the appropriate receiver
Example: a _log4j.udp.local. service name with an optional "decoder" property
could be advertised or received to automatically construct a UDPReceiver
2. define new service names which provide all needed information
Examples: a UDPReceiver could advertise that it can receive events by defining
a service name of _log4j_xml_accept_receive._udp.local., or a UDPReceiver could
automatically be created if an external system advertised
_log4j_xml_connect_send._udp.local.
One reason for using names would be if the external system's zeroconf
implementation couldn't provide properties.
--
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]
