From log4j-dev-return-5001-qmlist-jakarta-archive-log4j-dev=nagoya.apache.org@jakarta.apache.org Thu Jul 17 21:53:41 2003 Return-Path: Delivered-To: apmail-jakarta-log4j-dev-archive@apache.org Received: (qmail 76160 invoked from network); 17 Jul 2003 21:53:40 -0000 Received: from exchange.sun.com (192.18.33.10) by daedalus.apache.org with SMTP; 17 Jul 2003 21:53:40 -0000 Received: (qmail 2693 invoked by uid 97); 17 Jul 2003 21:56:16 -0000 Delivered-To: qmlist-jakarta-archive-log4j-dev@nagoya.betaversion.org Received: (qmail 2686 invoked from network); 17 Jul 2003 21:56:16 -0000 Received: from daedalus.apache.org (HELO apache.org) (208.185.179.12) by nagoya.betaversion.org with SMTP; 17 Jul 2003 21:56:16 -0000 Received: (qmail 75882 invoked by uid 500); 17 Jul 2003 21:53:37 -0000 Mailing-List: contact log4j-dev-help@jakarta.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Subscribe: List-Help: List-Post: List-Id: "Log4J Developers List" Reply-To: "Log4J Developers List" Delivered-To: mailing list log4j-dev@jakarta.apache.org Received: (qmail 75868 invoked from network); 17 Jul 2003 21:53:37 -0000 Received: from unknown (HELO ike.local.anstat.com.au) (202.92.123.11) by daedalus.apache.org with SMTP; 17 Jul 2003 21:53:37 -0000 Received: by ike.local.anstat.com.au with Internet Mail Service (5.5.2655.55) id <3H6R3QXT>; Fri, 18 Jul 2003 07:53:42 +1000 Message-ID: <7395B46C07F8D51182AE000629570CC4B2E36E@ike.local.anstat.com.au> From: Paul Smith To: 'Log4J Developers List' Subject: RE: I'm back... Date: Fri, 18 Jul 2003 07:53:32 +1000 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2655.55) Content-Type: text/plain; charset="iso-8859-1" X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N Welcome back, hope it was a very refreshing break. I can't speak for the XML side of things, but from the SocketAppender/SocketNode side of things: * Exposed a private static final default port variable as public * Modified the SocketNodeEventListener framework - allow listeners to know when the socket node is closed, and allow more than a single listener * Allow a SocketNode not to post events if it is 'paused' (this I am sure is one we'll tweak, the whoe active/paused concept is a little weak right now) * SocketReceiver - the ability to modify it via an external source, so modified shutdown operations, and ability to expose the current list of 'child' Sockets that are currently connected via this Receiver (These too should be 'closeable'). I'm still stuck in the middle of some heavy project work here, so my chainsaw coding has been zip over the last few weeks, but I'm lurking for discussions. cheers, Paul > -----Original Message----- > From: Mark Womack [mailto:mwomack@bevocal.com] > Sent: Friday, 18 July 2003 2:06 AM > To: Log4j-Dev (E-mail) > Subject: I'm back... > > > ...from vacation. I've been lurking for a few days, getting > back up to > speed at home and work. > > I want to start a review of the socket/xml related changes > next week. Can > Scott or Paul provide an overall roadmap of the changes in > these areas? > > -Mark > > --------------------------------------------------------------------- > To unsubscribe, e-mail: log4j-dev-unsubscribe@jakarta.apache.org > For additional commands, e-mail: log4j-dev-help@jakarta.apache.org > --------------------------------------------------------------------- To unsubscribe, e-mail: log4j-dev-unsubscribe@jakarta.apache.org For additional commands, e-mail: log4j-dev-help@jakarta.apache.org