You are viewing a plain text version of this content. The canonical link for it is here.
Posted to proton@qpid.apache.org by "Philip Harvey (JIRA)" <ji...@apache.org> on 2013/06/25 13:09:19 UTC
[jira] [Updated] (PROTON-343) Add a pluggable Proton logging layer
[ https://issues.apache.org/jira/browse/PROTON-343?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Philip Harvey updated PROTON-343:
---------------------------------
Attachment: 0001-PROTON-343-sketched-out-the-Java-parts-of-the-propos.patch
Skeleton implementation of a proton-j ("operational") logging design, intended to act as a "straw man" when discussing the design.
> 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. This logging needs to be "pluggable" - applications should be able to provide their own Proton logging implementation that, for example, uses their preferred logging framework.
> Proton's log output is considered to be part of its public interface. Therefore, this output should be consistent between proton-c and proton-j.
--
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