You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@qpid.apache.org by "ASF subversion and git services (JIRA)" <ji...@apache.org> on 2014/01/03 19:57:51 UTC
[jira] [Commented] (QPID-5415) Implement logging control in
qpid::messaging API
[ https://issues.apache.org/jira/browse/QPID-5415?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13861775#comment-13861775 ]
ASF subversion and git services commented on QPID-5415:
-------------------------------------------------------
Commit 1555202 from [~astitcher] in branch 'qpid/trunk'
[ https://svn.apache.org/r1555202 ]
QPID-5415: Implement control of internal log output in qpid::messaging API
> 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
>
> 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