You are viewing a plain text version of this content. The canonical link for it is here.

Posted to proton@qpid.apache.org by "Andrew Stitcher (JIRA)" <ji...@apache.org> on 2014/12/12 21:48:13 UTC

[jira] [Resolved] (PROTON-769) Simplify the trace flag logic by only keeping a single copy

     [ https://issues.apache.org/jira/browse/PROTON-769?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Andrew Stitcher resolved PROTON-769.
------------------------------------
       Resolution: Fixed
    Fix Version/s: 0.9

> Simplify the trace flag logic by only keeping a single copy
> -----------------------------------------------------------
>
>                 Key: PROTON-769
>                 URL: https://issues.apache.org/jira/browse/PROTON-769
>             Project: Qpid Proton
>          Issue Type: Improvement
>          Components: proton-c
>            Reporter: Andrew Stitcher
>            Assignee: Andrew Stitcher
>             Fix For: 0.9
>
>
> The code that produces log output in Proton C is split into multiple places in the code. It would make more sense to me to centralise the trace flags into the pn_transport_t object to as currently the logging API is there but the flags are duplicated.
> As an aside it would also make sense to introduce some new flags to allow control of logging at other levels besides Frame dumps and Raw frame bytes. I'd suggest PN_TRACE_DBG for debug tracing and maybe INF for more informational messages.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)