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 2013/02/12 15:33:14 UTC

[jira] [Comment Edited] (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:comment-tabpanel&focusedCommentId=13576611#comment-13576611 ] 

Bozo Dragojevic edited comment on PROTON-234 at 2/12/13 2:33 PM:
-----------------------------------------------------------------

There is also a kind of followup set of patches that merge in all the other submitted fixes and improvements
(PROTON-200, PROTON-230, PROTON-231, PROTON-233, PROTON-234)
and adds logging to those places, too. https://github.com/ttlj/qpid-proton/commits/upstream-all
                
      was (Author: bozzo):
    There is also a kind of followup set of patches that merge in all the other submitted fixes and improvements
and adds logging to those places, too. https://github.com/ttlj/qpid-proton/commits/upstream-all

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