Mailing-List: contact dev-help@qpid.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@qpid.apache.org
MIME-Version: 1.0
In-Reply-To: <30474676.91621283253534136.JavaMail.jira@thor>
References: <5940568.90501283247472917.JavaMail.jira@thor>
	<30474676.91621283253534136.JavaMail.jira@thor>
Date: Wed, 1 Sep 2010 19:12:55 +0100
Message-ID: <AANLkTikCc6Lx+wXUdOi_1zkLHMVGMoBbTMfNHzFT4LT9@mail.gmail.com>
Subject: Re: [jira] Updated: (QPID-2835) Implement connections (CON)
 operational logging on 0-10
From: Martin Ritchie <ritchiem@apache.org>
To: dev@qpid.apache.org
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

Hi Sorin,
I've been watching your changes wrt the Operational Logging apologies
for not replying to your thread over the weekend but I wasn't at a
computer.

I think the addition of the toLogString() is the wrong approach here.
The responsibility for the logging format should not lie with the
individual model objects.

>From our discussion on QPID-2780 this doesn't seem like the same
approach you are now taking, what changed?

The change suggested by the patch on QPID-2835 will introduce
inconsistency in the operation logging. Something that its
introduction was designed to reduce.

The LogActors are that point where the consistency is gained.
By locating the LogFormat and the string builder in one location the
LogActor has full responsibility of formatting log messages.

The approach that I would have taken here is to expose the required
common methods for logging on our Session and Connection models. This
would then mean that we would have two clean interfaces boundaries:
LogActors <-> Logging Framework
LogActors <-> Model Objects

This would mean that the desire to move to slf4j would be a matter of
adjusting the Logging Framework and the adding consistent 1-0 logging
would be simply a matter of implementing the model interfaces.

The only code that I would expect to see added to the 0-10 Connection
code paths is the introduction of Logging commands. The 0-10 Model
Objects should have nothing to do with formatting logging statements.

Cheers
Martin

On 31 August 2010 12:18, Sorin Suciu (JIRA)
<qpid-dev@incubator.apache.org> wrote:
>
> =C2=A0 =C2=A0 [ https://issues.apache.org/jira/browse/QPID-2835?page=3Dco=
m.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
>
> Sorin Suciu updated QPID-2835:
> ------------------------------
>
> =C2=A0 =C2=A0Attachment: qpid-2835.patch
>
>> Implement connections (CON) operational logging on 0-10
>> -------------------------------------------------------
>>
>> =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 Key: QPID-2835
>> =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 URL: https://iss=
ues.apache.org/jira/browse/QPID-2835
>> =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 Project: Qpid
>> =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0Issue Type: Improvement
>> =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0Components: Java Broker
>> =C2=A0 =C2=A0Affects Versions: 0.7
>> =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0Reporter: Sorin Suciu
>> =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0Priority: Minor
>> =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 Fix For: 0.7
>>
>> =C2=A0 =C2=A0 =C2=A0 =C2=A0 Attachments: qpid-2835.patch
>>
>>
>> This is part of the Qpid-2801, dealing with connection operational loggi=
ng on 0-10 code path.
>
> --
> This message is automatically generated by JIRA.
> -
> You can reply to this email to add a comment to the issue online.
>
>
> ---------------------------------------------------------------------
> Apache Qpid - AMQP Messaging Implementation
> Project: =C2=A0 =C2=A0 =C2=A0http://qpid.apache.org
> Use/Interact: mailto:dev-subscribe@qpid.apache.org
>
>


--=20
Martin Ritchie

---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project:      http://qpid.apache.org
Use/Interact: mailto:dev-subscribe@qpid.apache.org