Someone has to make the first move in the dance ;) 

-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Scott Deboy
Sent: Friday, September 16, 2005 9:26 AM
To: Log4J Users List
Subject: RE: Article: Yahoo Messenger Appender

correction:

If other frameworks started writing receivers, then there would be a reason to 
write an XMLSocketAppender.

-----Original Message-----
From: Scott Deboy [mailto:[EMAIL PROTECTED]
Sent: Fri 9/16/2005 7:21 AM
To: Log4J Users List
Subject: RE: Article: Yahoo Messenger Appender
 
There is an XMLSocketReceiver that can accept events from log4cxx, log4perl, 
java.util.logging and log4php.  UDPReceiver can be used to accept events from 
log4net.  

They all leverage the log4j.dtd (except java.util.logging of course, in which 
case you specify a UtilLogging XMLDecoder on the receiver side).

I didn't write an XMLSocketAppender because log4j already provides a way to 
send events over TCP: SocketAppender. 

If other frameworks started writing receivers, then there would be a reason to 
write an XMLSocketReceiver.

Scott

-----Original Message-----
From: Schuweiler, Joel J. [mailto:[EMAIL PROTECTED]
Sent: Fri 9/16/2005 6:36 AM
To: 'Log4J Users List'
Subject: RE: Article: Yahoo Messenger Appender
 
If I were to "brag" or write an article on an up and coming appender I would 
like to see one that works across all the log4* stuff. A socket appender which 
doesn't serialize objects but communicates in a pre-determined way.

After all, java is operating system independent, why not make it programming 
language independent (in the log4j sense) too?

I know how hard it would be to get the log4* projects to decide on one way, but 
it's a thought. 

-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Venkatray Kamath
Sent: Friday, September 16, 2005 8:33 AM
To: 'Log4J Users List'
Subject: RE: Article: Yahoo Messenger Appender

Also I also guess ym doesn't receive the message from same user more than 2
times unless the receiver responds back with some message.



-----Original Message-----
From: Schuweiler, Joel J. [mailto:[EMAIL PROTECTED]
Sent: Friday, September 16, 2005 7:00 PM
To: 'Log4J Users List'
Subject: RE: Article: Yahoo Messenger Appender

Re-connect everytime since you're making the new YahooMessengerAPI every
time.
Seems a bit taxing.

-----Original Message-----
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]
On Behalf Of Ron Grabowski
Sent: Friday, September 16, 2005 8:29 AM
To: Log4J Users List
Subject: Re: Article: Yahoo Messenger Appender

 protected void append(LoggingEvent event) {
  new  YahooMessengerAPI().sendYahooIM(
   getFromYahooId(),
   getFromYahooIdPassword(),
   getToYahooId(),
   (String)event.getMessage());
 }

I wonder if that keeps the YIM client logged in while the application
is running or if it connects and disconnects for each message?

--- James Stauffer <[EMAIL PROTECTED]> wrote:

> http://today.java.net/pub/a/today/2005/09/16/errors-via-yahoo-im.html
> --
> James Stauffer
> Are you good? Take the test at http://www.livingwaters.com/good/
>
> ---------------------------------------------------------------------
> 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]

---------------------------------------------------------------------
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]

Reply via email to