qpid-proton mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF subversion and git services (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (PROTON-343) Add a pluggable Proton logging layer
Date Wed, 04 Dec 2013 15:47:35 GMT

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

ASF subversion and git services commented on PROTON-343:
--------------------------------------------------------

Commit 1547827 from rhs@apache.org in branch 'proton/trunk'
[ https://svn.apache.org/r1547827 ]

PROTON-343: added logging callback for proton-c

> 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.



--
This message was sent by Atlassian JIRA
(v6.1#6144)

Mime
View raw message