As far as I understand log4j takes the log object and serializes it before sending it via socketappender. I have a feeling this will greatly limit "complete control".
-----Original Message----- From: Benjamin David [mailto:[EMAIL PROTECTED] Sent: Wednesday, August 17, 2005 10:41 AM To: Log4J Users List Subject: Re: WriterAppender to sockets When using SocketAppender / SocketHubAppender , Log4j sends the log info to a log server which listens to a socket. However, I want to send the log info to a socket which I will have complete control over, without using the log server infrastructure. Thanks, Ben On 8/17/05, Bradley, Todd <[EMAIL PROTECTED]> wrote: > > I do not want to use the SocketAppender as I need to log to > > the socket itself. > > I don't understand this sentence. SocketAppender and > SocketHubAppender are both ways of "logging to a socket" > so there must be something I'm missing here. > > > Todd. > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
