yes I suppose I could tell it to only send the message part after all, I
just need to pour through the documentation :). however what I was
hoping for was a clean way to receive it in my C program, u know without
50 lines of code :), maybe a premade library for such a purpose? When
you mentioned it I looked and it is XMLSocketAppender but I found that
through an online search and ran across some documentation, however it
may actually only be supported in the development or one of the dropped
versions. So I probably need to choose SocketAppender and then use an
XML layout. Thanks for pointing that out.

On Tue, 2007-10-30 at 10:27 +0100, Maarten Bosteels wrote:
> Is there an XMLSocketAppender in log4j ?
> Maybe in one of the extras ?
> 
> Anyhow, it's trivial to change SocketAppender to use the XmlLayout instead
> of java serialization.
> I already did, because I was comparing the speed (and size) of java
> serialization. with other exchange formats (XmlLayout, Hessian, ...) the
> test is not yet finished, but I think java serialization has no real
> advantages over using XmlLayout
> 
> I think log4j should have a SocketAppender that supports plugging in a
> Layout.
> 
> For your specific scenario, you could even adapt SocketAppender to only
> write the rendered logMessage on the socket
> since that's only thing your client program is interested in, right ?
> 
> Maarten
> 
> On 10/29/07, Neal Piche <[EMAIL PROTECTED]> wrote:
> >
> > the only reason I chose to use the XMLSocketAppender is because I read
> > that the regular socket appender uses serialized objects. I can change
> > what I am using I just don't know what to use. this is what I want to
> > happen: When the logging program sends a logging event I want a copy of
> > it to be picked up in my program so that I can parse the info and show a
> > tooltip letting me know about it. Can anyone tell me the best way to do
> > that? Oh the thing I can't change is the second program being in C.
> >
> >
> > ---------------------------------------------------------------------
> > 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]

Reply via email to