[
https://issues.apache.org/jira/browse/QPID-2248?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12786938#action_12786938
]
Ken Giusti commented on QPID-2248:
----------------------------------
My summary is a bit oversimplified: I'm proposing that we move the distinction
between what is a "statistic" and what is a non-statistic out of the functional
API and make it part of the schema that describes the data instead.
This results in QMF not needing to know if a bit of data is considered a
"statistic" or a "property" - that's left to the application that uses the
data. QMF becomes more data-agnostic.
An additional benefit is that this simplifies the API proper quite a bit.
Looking at the code as it stands now, for every "getProperty()"-like call,
there is a parallel "getStatistic()" call. In reality, QMF doesn't really
distinguish between the two. Removing this distinction in the API makes a lot
of code duplication go away.
We kept the term "property" because it's generic - it now applies to all data
(non-method) items.
thanks,
-K
> QMF: proposed API for QMFv2
> ----------------------------
>
> Key: QPID-2248
> URL: https://issues.apache.org/jira/browse/QPID-2248
> Project: Qpid
> Issue Type: New Feature
> Components: Qpid Managment Framework
> Reporter: Ken Giusti
> Assignee: Ted Ross
> Attachments: qmf-ng-api-12012009.txt, qmf-ng-api-12042009.patch,
> qmf-ng-api-12042009.txt
>
>
> Track the evolution of the QMFv2 api document.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:[email protected]
