[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]
Subject: RE: [wsia][wsia-requirements][E903]
See below.
-----Original Message-----
From: Wilson, Kirk [mailto:Kirk.Wilson@ca.com]
Sent: Tuesday, May 07, 2002 18:10
To: Alan Kropp; 'Rich Thompson'; 'wsia@lists.oasis-open.org'
Subject: RE: [wsia][wsia-requirements][E903]
E903
When a Producer has returned a Handle in response to a Consumer
invocation, the Consumer must ensure that Handle is supplied as a parameter
in any future invocations involving the Consumer and this Producer.
Excuse me if my questions are dumb--this is my first attempt to comment on
work that I still impresses me. I apologize that other commitments kept me
from participating in the committees discussions around the time of the F2F.
Isn't this formulation a bit too word?
"When a Producer has returned a Handle in response to a Consumer
invocation...": When else does a Producer "return" a Handle?
>>> Not all "consumer invocations" _return_ a handle. Thus, only "when a
producer has returned a handle...".
"the Consumer...invocations involving the Consumer..." Maybe I'm missing
something here, but does the Consumer ever not involve itself?
>>> I agree - this is a bit wordy.
Suggested revision: When a Producer has returned a Handle, the Consumer must
ensure that that Handle is supplied as a parameter in any future invocations
involving that Producer.
>>> I like that, except for the fact that some people (including me!)
thought that the use of "Handle" in a requirements document is not right, as
the concept of "Handle" is more of a interface specification type of entity.
So that I might better understand what is involved in this situation, Why
does the Producer need to have the Handle returned to it? What will it do
with it? (Just return it?)
>>> Actually, your suggested revision suggests to me that you understood the
requirement completey.
Also, the original requirement statement seemed to say something more than
stipulate a standard for Handle passing. It was specifically concerned with
how the Producer indicates which ACTIONS, etc. must be directed to a
stateful connection (vs. what I would assume to be the initial current
stateless connection). But I assume that might be clear from the signature
of a stateful service that it requires a Handle. But couldn't the Consumer
call on the Producer for another stateless service? Thus, the phrase "any
future invocations" might be too broad.
>>> Good point. How about "_some_ future invocations"?
Kirk Wilson
Computer Associates
Manager (Aion)
Tele: 603-823-4023
Fax: 603-823-4025
mailto:kirk.wilson@ca.com
-----Original Message-----
From: Alan Kropp [mailto:akropp@epicentric.com]
Sent: Monday, May 06, 2002 12:42 PM
To: 'Rich Thompson'; 'wsia@lists.oasis-open.org'
Subject: RE: [wsia][wsia-requirements][E903]
Yes, that seems clearer Rich.
-----Original Message-----
From: Rich Thompson [mailto:richt2@us.ibm.com]
Sent: Monday, May 06, 2002 4:21 AM
To: 'wsia@lists.oasis-open.org'
Subject: Re: [wsia][wsia-requirements][E903]
The Producer is always invoked by the Consumer (may be as part of
coordination/orchestration). I'm not sure what it means to embed a
parameter and I question whether we need to call out that the Handle may
only be part of a response. Reword to:
E903
When a Producer has returned a Handle in response to a Consumer
invocation, the Consumer must ensure that Handle is supplied as a parameter
in any future invocations involving the Consumer and this Producer.
Alan Kropp
<akropp@epicentri To:
"'wsia@lists.oasis-open.org'"
c.com> <wsia@lists.oasis-open.org>
cc:
05/03/2002 09:48 Subject:
[wsia][wsia-requirements][E903]
PM
E903
The specification must specify the means by which
a Producer
indicates which actions, events and operations are to be redirected to the
stateful connection between the Consumer and Producer.
Reword to sync with E902:
E903
When a Producer has returned a Handle as part of
the
response to an End User invocation, the Consumer must ensure that Handle is
embedded as a parameter in any future invocations involving the End User
and
this Producer.
----------------------------------------------------------------
To subscribe or unsubscribe from this elist use the subscription
manager: <http://lists.oasis-open.org/ob/adm.pl>
----------------------------------------------------------------
To subscribe or unsubscribe from this elist use the subscription
manager: <http://lists.oasis-open.org/ob/adm.pl>
----------------------------------------------------------------
To subscribe or unsubscribe from this elist use the subscription
manager: <http://lists.oasis-open.org/ob/adm.pl>
----------------------------------------------------------------
To subscribe or unsubscribe from this elist use the subscription
manager: <http://lists.oasis-open.org/ob/adm.pl>
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]
Powered by eList eXpress LLC