The version of Apache log4j used by SoundHelix.
Clone
HTTPS:
git clone https://vervis.peers.community/repos/aEp6o
SSH:
git clone USERNAME@vervis.peers.community:aEp6o
Branches
Tags
- 1.3alpha-7
- CHAINSAW_2_SANDBOX_MERGE
- CORE_VERSION
- LEVEL_REPLACES_PRIORITY
- PREALPHA_1_3_AS_OF_2004_05_12
- PRE_CHAINSAW_MODEL_CONVERSION
- PRE_UGLI_MOVE
- TAG_CHAINSAW2_MOVE
- log4j-1.2.17
- log4j-1.2.17-rc1
- v1.3alpha8
- v1.3alpha8-temp
- v1_2_1
- v1_2_10-recalled
- v1_2_11
- v1_2_11_rc1
- v1_2_11rc3
- v1_2_12
- v1_2_12_rc1
- v1_2_12_rc2
- v1_2_12_rc3
- v1_2_12_rc4
- v1_2_12_rc5
- v1_2_12_rc6
- v1_2_13
- v1_2_13_rc1
- v1_2_13_rc2
- v1_2_13_site_update
- v1_2_14
- v1_2_14_maven
- v1_2_14_rc1
- v1_2_14_site_update
- v1_2_15
- v1_2_15_rc1
- v1_2_15_rc2
- v1_2_15_rc3
- v1_2_15_rc4
- v1_2_15_rc5
- v1_2_15_rc6
- v1_2_16
- v1_2_16_rc1
- v1_2_16_rc2
- v1_2_17
- v1_2_17-rc1
- v1_2_17_rc1
- v1_2_17_rc2
- v1_2_17_rc3
- v1_2_2
- v1_2_3
- v1_2_4
- v1_2_6
- v1_2_7
- v1_2_9
- v1_2_alpha0
- v1_2_alpha7
- v1_2beta1
- v1_2final
- v1_3alpha_1
- v1_3alpha_6
- v_1_0
- v_1_0_1
- v_1_0_4
- v_1_1
- v_1_1_1
- v_1_1_2
- v_1_1_3
- v_1_1_b1
- v_1_1b2
- v_1_1b3
- v_1_1b5
- v_1_1b6
- v_1_1b7
- v_1_2beta3
mail-2001-02-07
Delivered-To: urba-cgu@urbanet.ch
Mailing-List: contact log4j-dev-help@jakarta.apache.org; run by ezmlm
List-Post: <mailto:log4j-dev@jakarta.apache.org>
List-Help: <mailto:log4j-dev-help@jakarta.apache.org>
List-Unsubscribe: <mailto:log4j-dev-unsubscribe@jakarta.apache.org>
List-Subscribe: <mailto:log4j-dev-subscribe@jakarta.apache.org>
Reply-To: "LOG4J Developers Mailing List" <log4j-dev@jakarta.apache.org>
Delivered-To: mailing list log4j-dev@jakarta.apache.org
From: Kitching Simon <Simon.Kitching@orange.ch>
To: "'log4j-dev@jakarta.apache.org'" <log4j-dev@jakarta.apache.org>
Subject: PATCH: New classes: DatagramStreamAppender & friends
Date: Wed, 7 Feb 2001 12:41:54 +0100
X-Mailer: Internet Mail Service (5.5.2650.21)
X-Spam-Rating: h31.sny.collab.net 1.6.2 0/1000/N
Hi log4j developers....
Here, for your consideration, is a set of files that
implement an Appender which sends messages
to a remote host/port via UDP (datagram).
There was brief discussion of this Appender on the
log4j-user group, about a week ago. Ceki suggested
that the Appender send serialized log event objects
over UDP; while this approach has a number of
advantages, I have decided to instead perform the
message formatting at the client end, mainly so
that:
(a) the UDP server application does not have to be in java
(b) non-java clients can send messages to the same UDP
server.
The appender has been named "DatagramStringAppender"
to allow someone to write a serialization-based version at
some later time, if desired, without any name confusion.
------------------------------
Notes:
DatagramStringAppender is based on SyslogAppender, but
with a fair number of changes.
DatagramStringWriter is based on SyslogWriter, with a few changes.
In particular, it takes an "encoding" parameter, so that the character
encoding used can be specified, and a "port".
SingleLineTracerPrintWriter is almost identical to
SyslogTracerPrintWriter; just the name & some comments
have changed. [I didn't want to call a class called SyslogXXX
from the DatagramStreamAppender classes]
------------------------------
If this patch is accepted, then it may be worth rewriting SyslogAppender
to use the DatagramStringWriter and SingleLineTracerPrintWriter
classes. These classes should be compatible with SyslogAppender,
as they implement the same functionality, or a superset of the
Syslog functionality, and have more "general" names.
------------------------------
<<DatagramStringAppender.java>>
<<DatagramStringWriter.java>>
<<SingleLineTracerPrintWriter.java>>
--------------------------------
And here's a simple perl UDP server, and an xml
config file for testing the appender.
<<logconfig.xml>>
<<udpserver.pl>>
Regards,
Simon