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

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

Commit 1501276 from [~philharveyonline]
[ https://svn.apache.org/r1501276 ]

PROTON-343: initial implementation of logging, including the central class 
ProtonLogger
and category logger implementations for java.util.logging (the default), 
standard out and SLF4J.
Still to do:
- Implementations in proton-jni and proton-c
- Define the full set of logging functions in EngineLogger et al.
- Modify existing Proton classes to actually use the new logging classes.
                
> 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
>         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 is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Reply via email to