You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@qpid.apache.org by "Ken Giusti (JIRA)" <ji...@apache.org> on 2016/02/16 21:10:18 UTC
[jira] [Resolved] (QPID-7064) Document Asynchronous Error
Notification API on Connection, Session, Receiver, and Sender objects
[ https://issues.apache.org/jira/browse/QPID-7064?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ken Giusti resolved QPID-7064.
------------------------------
Resolution: Fixed
Assignee: Ken Giusti
Fix Version/s: qpid-python-next
The fix for QPID-7053 contains the requested documentation updates.
> Document Asynchronous Error Notification API on Connection, Session, Receiver, and Sender objects
> -------------------------------------------------------------------------------------------------
>
> Key: QPID-7064
> URL: https://issues.apache.org/jira/browse/QPID-7064
> Project: Qpid
> Issue Type: Bug
> Components: Python Client
> Affects Versions: 0.32
> Reporter: Brian Bouterse
> Assignee: Ken Giusti
> Priority: Minor
> Labels: docuentation
> Fix For: qpid-python-next
>
>
> With the fixing of QPID-7053 an asynchronous exception notification callback is added to the Connection, Session, Receiver, and Sender objects in qpid.messaging. The purpose and usage of this is not immediately obvious and would benefit from documentation being added. It also needs to explain that it is forbidden to call back in qpid.messaging from within the callback handler. Also it needs to identify the required function signature that the developer must adhere to to create a usable callback and then how to register it.
> I propose this documentation be added at the object level so it appears in the main-page of each object type and not at the function level.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@qpid.apache.org
For additional commands, e-mail: dev-help@qpid.apache.org