MHonArc v2.5.2 -->
wsia message
[Date Prev]
| [Thread Prev]
| [Thread Next]
| [Date Next]
--
[Date Index]
| [Thread Index]
| [Elist Home]
Subject: Re: [wsia] [wsia-requirements][E907]
I think the intent here is to capture a significant reduction in network
overhead without a significant increase in complexity. Since this
requirement (even as you have rewritten it) could be accomplished either by
batching operation invocations (supported by all web service stacks?) or by
defining batch oriented operations, I think the intent can be accomplished.
I think the batching of dissimilar operations raises a lot of issues, some
of which will be out of the domain of this committee and therefore should
not be covered as a requirement (though we may want to drive the issues
onto the relevant standards committees).
As far as the expansion of this requirement involved in your rewrite, do we
want to require the create, update, delete AND read can all be done in a
single operation? Basically, does combining read and write create more
confusion than it is worth?
"Quintas, Peter"
<Peter.Quintas@di To: wsia@lists.oasis-open.org
vine.com> cc:
Subject: [wsia] [wsia-requirements][E907]
05/06/2002 09:31
AM
E907
It should be possible for a Consumer to batch update multiple
properties of the Producer with one invocations.
Debate: GT, PQ, TC, SR, WC, RT.
Debate whether this is true for all WSIA operations.
I think the edit we came up with is fine, althought I also think that
this *is* true for all (or most) WSIA operations. The problem I have
is that as requirements we may want to single out operations that can
be performed in batch to simplify our scope. All WSIA operations can
be done in batch, but this may be to complex a specification for rev
1. I imagine there might be some more complex state management if
getMarkup() or invokeAction() were able to be invoked in batch.
Therefore, I propose that we might want to keep this requirement for
only properties at this time. I would expand the requirement (or add
more reqs) to encompass reading properties and performing updates and
reads along with other operations (for example, getMarkup() or
invokeAction()). I would also expand the definition to encompass all
types of "updates" for clarity.
New edit:
It should be possible for a Consumer to batch create, read, update
and delete multiple properties of the Producer with one invocation.
It should also be possible to perform this operation in conjunction
with other operations.
Question: What other operations might be perform in batch they we would
want to include in the reqs, if any?
Thanks,
peter j quintas
director of technology
web services infrastructure lab
divine, inc.
main: +1 312 606 8100
direct: +1 312 606 8124
mobile: +1 312 953 7845
fax: +1 312 896 5972
peter.quintas@divine.com
[Date Prev]
| [Thread Prev]
| [Thread Next]
| [Date Next]
--
[Date Index]
| [Thread Index]
| [Elist Home]
Powered by eList eXpress LLC