qpid-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ted Ross (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (QPID-3275) QMF Console asynchronous correlation-id should be scoped to the session, not the specific agent
Date Tue, 24 May 2011 14:27:47 GMT

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

Ted Ross updated QPID-3275:
---------------------------

          Component/s: Qpid Managment Framework
    Affects Version/s: 0.10
        Fix Version/s: 0.11

> QMF Console asynchronous correlation-id should be scoped to the session, not the specific
agent
> -----------------------------------------------------------------------------------------------
>
>                 Key: QPID-3275
>                 URL: https://issues.apache.org/jira/browse/QPID-3275
>             Project: Qpid
>          Issue Type: Improvement
>          Components: Qpid Managment Framework
>    Affects Versions: 0.10
>            Reporter: Ted Ross
>            Assignee: Ted Ross
>            Priority: Minor
>             Fix For: 0.11
>
>
> When using asynchronous operations from the qmf console (qmf::ConsoleSession), the correlation-id
returned is scoped to the specific agent.  This forces the user to combine the agent identity
with the correlation-id to correlate ta response to a request.  It would be more efficient
if the correlation-id were guaranteed unique across all agents in the session.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project:      http://qpid.apache.org
Use/Interact: mailto:dev-subscribe@qpid.apache.org


Mime
View raw message