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

Posted to dev@qpid.apache.org by "Andrew Stitcher (JIRA)" <ji...@apache.org> on 2014/01/03 20:11:51 UTC

[jira] [Resolved] (QPID-5415) Implement logging control in qpid::messaging API

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

Andrew Stitcher resolved QPID-5415.
-----------------------------------

       Resolution: Implemented
    Fix Version/s: 0.27

> Implement logging control in qpid::messaging API
> ------------------------------------------------
>
>                 Key: QPID-5415
>                 URL: https://issues.apache.org/jira/browse/QPID-5415
>             Project: Qpid
>          Issue Type: Improvement
>          Components: C++ Client
>            Reporter: Andrew Stitcher
>            Assignee: Andrew Stitcher
>             Fix For: 0.27
>
>
> Currently there is one major omission from the qpid::messaging API: That is control of the internal logging used by qpid itself. This was present in the qpid::client API albeit not really supported or documented.
> This breaks down to 2 essential pieces and one optional one:
> *  Allow library client code control of the logging levels etc which are logged.
> *  Allow clients to handle logging output in a way that suits the application
> * (Optional) Allow clients to inject logged messages into the logging stream



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@qpid.apache.org
For additional commands, e-mail: dev-help@qpid.apache.org