Return-Path: 
 <log4j-dev-return-19209-apmail-logging-log4j-dev-archive=logging.apache.org@logging.apache.org>
X-Original-To: apmail-logging-log4j-dev-archive@www.apache.org
Delivered-To: apmail-logging-log4j-dev-archive@www.apache.org
Received: from mail.apache.org (hermes.apache.org [140.211.11.3])
	by minotaur.apache.org (Postfix) with SMTP id 6BAC19EBA
	for <apmail-logging-log4j-dev-archive@www.apache.org>;
 Mon, 23 Jul 2012 03:29:31 +0000 (UTC)
Received: (qmail 75682 invoked by uid 500); 23 Jul 2012 03:29:30 -0000
Delivered-To: apmail-logging-log4j-dev-archive@logging.apache.org
Received: (qmail 75493 invoked by uid 500); 23 Jul 2012 03:29:28 -0000
Mailing-List: contact log4j-dev-help@logging.apache.org; run by ezmlm
Precedence: bulk
List-Unsubscribe: <mailto:log4j-dev-unsubscribe@logging.apache.org>
List-Help: <mailto:log4j-dev-help@logging.apache.org>
List-Post: <mailto:log4j-dev@logging.apache.org>
List-Id: "Log4J Developers List" <log4j-dev.logging.apache.org>
Reply-To: "Log4J Developers List" <log4j-dev@logging.apache.org>
Delivered-To: mailing list log4j-dev@logging.apache.org
Received: (qmail 75402 invoked by uid 99); 23 Jul 2012 03:29:24 -0000
Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136)
    by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 23 Jul 2012 03:29:24 +0000
X-ASF-Spam-Status: No, hits=1.5 required=5.0
	tests=HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS
X-Spam-Check-By: apache.org
Received-SPF: pass (athena.apache.org: domain of scott.deboy@gmail.com
 designates 209.85.213.175 as permitted sender)
Received: from [209.85.213.175] (HELO mail-yx0-f175.google.com)
 (209.85.213.175)
    by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 23 Jul 2012 03:29:18 +0000
Received: by yenl13 with SMTP id l13so5192656yen.34
        for <log4j-dev@logging.apache.org>;
 Sun, 22 Jul 2012 20:28:57 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=gmail.com; s=20120113;
        h=mime-version:date:message-id:subject:from:to:content-type;
        bh=MwdEBnlN15rt4TbLlhbH5/mfY1M+IavOQO57fnPsGv4=;
        b=J+VnbrJnfKEVG6dzuj8TjPs06N+9qvMhaOg9/yWzln1/9fT2E7dS7oZbMz+6HvD1pW
         LbD+nOWoGV35qgRuPei92yoaet6VL3dnH/08n7e5Nd37/lBWsdVLTe4OXS1msWHe9+ni
         z9EtTIcxgUqmnkLoFinLTWmESNruhL6VMJCRnU7Y+GdWb1A3V0eZsRIlOaI1/mD45UAf
         gZKk9snRg5rAONjzBIpF0KnrROMCMFQRu+rciVDnGuk6QZ4mMWez9yU30GvIEoLoU4bS
         ey/ktpQ5ol0XLvnrpxxEo25hdNOX2aIFgGUNjN1QSL1lMsQky6T/PNTVTAEzvgg+0WLe
         aKow==
MIME-Version: 1.0
Received: by 10.66.75.98 with SMTP id b2mr13577372paw.60.1343014136877; Sun,
 22 Jul 2012 20:28:56 -0700 (PDT)
Received: by 10.142.80.12 with HTTP; Sun, 22 Jul 2012 20:28:56 -0700 (PDT)
Date: Sun, 22 Jul 2012 20:28:56 -0700
Message-ID: 
 <CADBq88As8MNhcGThLfGJ+2LEnWxQ-O3RLxNgJBVkMms22gkx6Q@mail.gmail.com>
Subject: Extras companion supported by log4j2?
From: Scott Deboy <scott.deboy@gmail.com>
To: Log4J Developers List <log4j-dev@logging.apache.org>
Content-Type: multipart/alternative; boundary=f46d042fdb7a8e906e04c576d84e
X-Virus-Checked: Checked by ClamAV on apache.org

--f46d042fdb7a8e906e04c576d84e
Content-Type: text/plain; charset=ISO-8859-1

I'm not sure how much of the extras companion would be applicable to
log4j2.  I assume appender and receiver-related things wouldn't change much
except for the construction of LoggingEvents?

I can look things over, but Ralph, if you wouldn't mind, would you give
extras a once-over and point out what is redundant with features already
provided by log4j2, and what changes other than event construction would be
likely in order to support extras with log4j2?

I'd like to support Chainsaw with log4j2 (and existing appenders and
receivers etc) and I don't yet have a sense for what that would take.

Scott

--f46d042fdb7a8e906e04c576d84e
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

I&#39;m not sure how much of the extras companion would be applicable to lo=
g4j2.=A0 I assume appender and receiver-related things wouldn&#39;t change =
much except for the construction of LoggingEvents?<br><br>I can look things=
 over, but Ralph, if you wouldn&#39;t mind, would you give extras a once-ov=
er and point out what is redundant with features already provided by log4j2=
, and what changes other than event construction would be likely in order t=
o support extras with log4j2? <br>
<br>I&#39;d like to support Chainsaw with log4j2 (and existing appenders an=
d receivers etc) and I don&#39;t yet have a sense for what that would take.=
<br><br>Scott<br>

--f46d042fdb7a8e906e04c576d84e--