Mark: Thank you so much for your such a clear and detailed explanation. Now, I understand how the SocketHubAppender works: SocketHubAppender defines a socket port which is the SOURCE of the logging event. Clients need to connect to the port(LoggingEvent SOURCE),and read LoggingEvent from that SOURCE.
Thank you again and I look forward for your sample code(When it's convenient for you). Best regards, Nancy ----- Original Message ----- From: "Mark Womack" <[EMAIL PROTECTED]> To: "'Log4J Users List'" <[EMAIL PROTECTED]> Sent: Tuesday, February 11, 2003 3:18 PM Subject: RE: Urgent---Help please > Nancy, > > > As the code showed above, it uses readObject of > > ObjectInputStream to get the > > LoggingEvent. I am a little confused here: the > > SocketHubAppender defines the > > destination of the LoggingEvent(in my case, the swing > > application is the > > destination of the LoggingEvent). From my understanding, when > > the log is > > requested from the web application, the LoggingEvent is > > automatically passed > > to destination(in my case, the swing application). Why we > > need to write code > > to get the LoggingEvent from the web application(as the code > > showed above)? > > Actually, SocketHubAppender defines a socket port which is the SOURCE of the > logging event, not the destination. SocketHubAppender "writes" > LoggingEvents to any clients that have connected to it (on it's configured > port). Clients must "read" the logging events. SocketAppender also > "writes" logging events, but it is different in that it is configured to > know about the specific socket host/port destination to send the events to. > > Your client code should be written to "connect" to the host/port the > SocketHubAppender is located at, and then read the logging events as in the > example code. I have some sample code that does this, but I cannot post it > until this evening. Your client should basically do what SocketAppender > does to connect to its destination. > > The current Chainsaw does not support SocketHubAppender, but only > SocketAppender (I have posted patches that fix this, and there are plans to > fix this in v1.3). So, in the current code, Chainsaw acts as a destination > for SocketAppender "writes". > > hth, > -Mark > > --------------------------------------------------------------------- > 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]
