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/03/25 21:11:24 UTC

[jira] Created: (QPID-877) Management protocol and API improvements

Management protocol and API improvements
----------------------------------------

                 Key: QPID-877
                 URL: https://issues.apache.org/jira/browse/QPID-877
             Project: Qpid
          Issue Type: Improvement
          Components: C++ Broker, Python Client
            Reporter: Ted Ross
            Priority: Minor


This patch provides the following management improvements:

1) The protocol now supports a simple GET operation for retrieving management content immediately from the broker.
2) Package and Schema queries to the broker now have their completions marked by a command-complete message (also used in the GET command).  This makes it easy to write simple, synchronous client code if desired.
3) The broker creates and stores a UUID for self-identification.  This can be used by management clients to track historical data over multiple broker restarts.
4) The management API now reports the broker UUID and the session UUID to its client via callback.


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


[jira] Closed: (QPID-877) Management protocol and API improvements

Posted by "Ted Ross (JIRA)" <qp...@incubator.apache.org>.
     [ https://issues.apache.org/jira/browse/QPID-877?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Ted Ross closed QPID-877.
-------------------------

    Resolution: Fixed

> Management protocol and API improvements
> ----------------------------------------
>
>                 Key: QPID-877
>                 URL: https://issues.apache.org/jira/browse/QPID-877
>             Project: Qpid
>          Issue Type: Improvement
>          Components: C++ Broker, Python Client
>            Reporter: Ted Ross
>            Priority: Minor
>         Attachments: qpid-patch26.diff
>
>
> This patch provides the following management improvements:
> 1) The protocol now supports a simple GET operation for retrieving management content immediately from the broker.
> 2) Package and Schema queries to the broker now have their completions marked by a command-complete message (also used in the GET command).  This makes it easy to write simple, synchronous client code if desired.
> 3) The broker creates and stores a UUID for self-identification.  This can be used by management clients to track historical data over multiple broker restarts.
> 4) The management API now reports the broker UUID and the session UUID to its client via callback.

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


[jira] Updated: (QPID-877) Management protocol and API improvements

Posted by "Ted Ross (JIRA)" <qp...@incubator.apache.org>.
     [ https://issues.apache.org/jira/browse/QPID-877?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Ted Ross updated QPID-877:
--------------------------

    Attachment: qpid-patch26.diff

Patch file (CPP and Python)

> Management protocol and API improvements
> ----------------------------------------
>
>                 Key: QPID-877
>                 URL: https://issues.apache.org/jira/browse/QPID-877
>             Project: Qpid
>          Issue Type: Improvement
>          Components: C++ Broker, Python Client
>            Reporter: Ted Ross
>            Priority: Minor
>         Attachments: qpid-patch26.diff
>
>
> This patch provides the following management improvements:
> 1) The protocol now supports a simple GET operation for retrieving management content immediately from the broker.
> 2) Package and Schema queries to the broker now have their completions marked by a command-complete message (also used in the GET command).  This makes it easy to write simple, synchronous client code if desired.
> 3) The broker creates and stores a UUID for self-identification.  This can be used by management clients to track historical data over multiple broker restarts.
> 4) The management API now reports the broker UUID and the session UUID to its client via callback.

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