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][E902]
We should be very careful about specifying the solution as a requirement.
As a requirement the standard must specify the means by which the Consumer
and Producer will communicate some reference to stateful information. The
concept of a handle is a nice clean, self-contained solution, but other
solutions might include central registries of GUIDs or even UUIDs.
Alan Kropp
<akropp@epicentri To: "'Gil Tayar'" <Gil.Tayar@webcollage.com>, Alan Kropp
c.com> <akropp@epicentric.com>, "'wsia@lists.oasis-open.org'"
<wsia@lists.oasis-open.org>
05/06/2002 12:35 cc:
PM Subject: RE: [wsia][wsia-requirements][E902]
>My question is - what is wrong with E902?
I'm unhappy with the vagueness of the second sentence: "Means by
which the Consumer gains access to the stateful connection must be well
defined."
We're hinting at something here, and rather than be coy about it, I think
we
should make a stronger statement. Your point that the "handle" concept
seems implementation-specific is valid. I'm open to suggestion as to how
to
express it better in the context of a requirements document.
Alan