Thus quoth Fred Carter (~ 10/14/2005 10:52 AM ~)...
Well, it's just a properties document. So whatever query mechanism for
that would have to do -- that's a WSDM limit, I think. So this would
use the QueryResourceProperties optional call with a query expression
(dialect XPath) of
*[namespace-uri()="this capability's namespace" and
./@operationName="desiredOperation"]
(or something like that)
An alternative, where the query function isn't required, would be to
name the operation metrics with the operation name. However, I think
we'd have a hard time coming up with a schema then (we'd need a meta
schema :-) ), since we wouldn't have the metric names at spec time
(since the operations vary quite a bit, obviously).
Yet another alternative is to add a WSDM-specific operation that does
this :: getOperationMetric(opName[, portType]) or something. Pretty
trivial to do...
At a higher level, the choice at some level, was either
individual metrics or a more general property document element for the
operation -- that would contain all the stuff about an operation.
This seemed counter to how we've done capabilities, so I separated it
this way.
The other choice involves a capability (or some combination thereof)
that instituted a subdocument for operation properties. I wasn't quite
sure if that was easily representable, so...
Thus quoth Tony Gullotta (~ 10/14/2005 10:34 AM ~)...
How would I request the NumberOfRequests metric for just one operation?
-----Original Message-----
From: fred.carter@amberpoint.com [mailto:fred.carter@amberpoint.com]
Sent: Friday, October 14, 2005 10:22 AM
To: wsdm@lists.oasis-open.org
Subject: [wsdm] Groups - OperationMetricsProposal (MowsOpMetrics.doc)
uploaded
This document proposes to extend the MUWS metrics capability, adding an
operation name &, optionally, portType, attributes to the current set of
MOWS metrics. As an example, we could report number of requests for the
sample operation as
<NumberOfRequests operationName="sample" ...>34</NumberOfRequests>
<NumberOfRequests operationName="anotherSample"
...>3</NumberOfRequests>
In this environment, any number of numberOfRequests is permitted, though
they must have different operationNames, or, if the same, different
portTypes, as these are the distinguishing characteristics.
Document current shows changes based on the MOWS Metrics capability
since it's pretty analogous.
It occurred to me that this is not all that hard, so we may be able to
fit it in (as was some folks recollection of the plan). My apologies to
Bryan as I think we were supposed to collaborate, but he's out of town
now, and I'll be out much of next week.
Feel free to shoot away on the list!
/fred
-- fred carter
The document named OperationMetricsProposal (MowsOpMetrics.doc) has been
submitted by fred carter to the OASIS Web Services Distributed
Management
(WSDM) TC document repository.
Document Description:
Operation Metrics Proposed Text
View Document Details:
http://www.oasis-open.org/apps/org/workgroup/wsdm/document.php?document_
id=14904
Download Document:
http://www.oasis-open.org/apps/org/workgroup/wsdm/download.php/14904/Mow
sOpMetrics.doc
PLEASE NOTE: If the above links do not work for you, your email
application may be breaking the link into two pieces. You may be able
to copy and paste the entire link address into the address field of your
web browser.
-OASIS Open Administration
--
Fred Carter / AmberPoint, Inc.
mailto:fred.carter@amberpoint.com
tel:+1.510.433.6525 fax:+1.510.663.6301
--
Fred Carter / AmberPoint, Inc.
mailto:fred.carter@amberpoint.com
tel:+1.510.433.6525 fax:+1.510.663.6301
|