You are viewing a plain text version of this content. The canonical link for it is here.
Posted to proton@qpid.apache.org by "Bozo Dragojevic (JIRA)" <ji...@apache.org> on 2015/10/08 21:57:27 UTC
[jira] [Closed] (PROTON-234) Add lots of logging to better
understand inner working of proton
[ https://issues.apache.org/jira/browse/PROTON-234?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Bozo Dragojevic closed PROTON-234.
----------------------------------
Resolution: Won't Fix
proton has outgrown these
> Add lots of logging to better understand inner working of proton
> ----------------------------------------------------------------
>
> Key: PROTON-234
> URL: https://issues.apache.org/jira/browse/PROTON-234
> Project: Qpid Proton
> Issue Type: Improvement
> Components: proton-c
> Reporter: Bozo Dragojevic
> Labels: logging
>
> Add lots of logging to proton to ease understnding of it's inner workings
> Introduce object naming facility as some layers are coupled really loosely
> for now the logging route will just dump everything out to stderr, as it was before
> This is currently one giant commit off 0.3: https://github.com/ttlj/qpid-proton/commits/upstream-logging
> It doesn't merge quite cleanly to trunk. If this is interesting thing to have I'd be willing to merge or rebase whichever is preferred.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)