You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@qpid.apache.org by "Ted Ross (JIRA)" <qp...@incubator.apache.org> on 2008/09/10 21:21:44 UTC

[jira] Resolved: (QPID-1279) Application level status communication

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

Ted Ross resolved QPID-1279.
----------------------------

       Resolution: Fixed
    Fix Version/s: M4

> Application level status communication
> --------------------------------------
>
>                 Key: QPID-1279
>                 URL: https://issues.apache.org/jira/browse/QPID-1279
>             Project: Qpid
>          Issue Type: New Feature
>          Components: C++ Broker
>            Reporter: Matthew Farrellee
>            Assignee: Ted Ross
>             Fix For: M4
>
>
> Applications using the QMF implementing Management Methods may well have to communicate status information between callers and callees. For some applications this status information may be complex and very application specific. However, for some applications this status may be simply FAIL and a textual message.
> Management methods can currently report STATUS_OK/../STATUS_FORBIDDEN (list in qpid/management/Manageable.h), and a textual message is automatically associated with each status. I propose a STATUS_FAIL and access to the textual message to cover the common case of applications that need simple status information passing.
> Adding a STATUS_FAIL does not appear to hi-jack the status information in QMF's infrastructure, as values such as STATUS_INVALID_PARAMETER and STATUS_FORBIDDEN already appear to allow the management method's implementation to communicate with the caller.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.