You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@qpid.apache.org by "Alan Conway (JIRA)" <qp...@incubator.apache.org> on 2007/11/15 21:51:43 UTC
[jira] Resolved: (QPID-687) Update to the protocol used for
management schema transfer
[ https://issues.apache.org/jira/browse/QPID-687?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Alan Conway resolved QPID-687.
------------------------------
Resolution: Fixed
Comitted qpid-patch7-cpp.diff qpid-patch7-python.diff r595453.
> Update to the protocol used for management schema transfer
> ----------------------------------------------------------
>
> Key: QPID-687
> URL: https://issues.apache.org/jira/browse/QPID-687
> Project: Qpid
> Issue Type: Improvement
> Components: C++ Broker, Python Client
> Reporter: Ted Ross
> Priority: Minor
> Attachments: qpid-patch7-cpp.diff, qpid-patch7-python.diff
>
>
> This update contains two patches: one for the C++ broker and one for the Python client.
> The patches update the protocol used to transfer the management schema to the management client. The new protocol uses field tables to carry mandatory and optional schema fields.
> Also in this update: The routing key structure has been brought in line with the document on the Wiki (http://cwiki.apache.org/qpid/management-design-notes.html#ManagementDesignnotes-RoutingKeyStructure). Each configuration or instrumentation update is now in its own AMQP message with a routing key that describes the object class and the type of update (schema, configuration, or instrumentation).
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.