atom feed2 messages in org.apache.qpid.proton[jira] [Commented] (PROTON-343) Add a...
FromSent OnAttachments
ASF subversion and git services (JIRA)Dec 4, 2013 7:47 am 
ASF subversion and git services (JIRA)Dec 5, 2013 5:06 am 
Subject:[jira] [Commented] (PROTON-343) Add a pluggable Proton logging layer
From:ASF subversion and git services (JIRA) (ji@apache.org)
Date:Dec 5, 2013 5:06:39 am
List:org.apache.qpid.proton

[
https://issues.apache.org/jira/browse/PROTON-343?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13840063#comment-13840063
]

ASF subversion and git services commented on PROTON-343:

--------------------------------------------------------

Commit 1548123 from rh@apache.org in branch 'proton/trunk' [ https://svn.apache.org/r1548123 ]

PROTON-343: added transport context

Add a pluggable Proton logging layer

------------------------------------

Key: PROTON-343 URL: https://issues.apache.org/jira/browse/PROTON-343 Project: Qpid Proton Issue Type: Improvement Components: proton-c, proton-j Reporter: Philip Harvey Assignee: Philip Harvey Fix For: 0.6

Attachments:
0001-PROTON-343-sketched-out-the-Java-parts-of-the-propos.patch

Applications that use Proton sometimes want Proton to produce logging. Goals ==== * Proton should provide a default logging implementation. * It should be easy for Proton client code to provide custom logging
implementation, e.g. one that uses the same third party logging framework as
their application code. * Proton should not have a compile-time dependency on a third party logging
framework * Proton's log output is considered to be part of its public interface.
Therefore, in the spirit of Proton's cross-language consistency goals, this
output should be consistent between proton-c and proton-j. * The goals that general-purpose logging frameworks try to meet - performance,
ease of use etc - also apply.