[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: RE: [ws-caf] interesting document
I have
to believe I'm missing something or being plain stupid, but here goes
...
It would be interesting, in light of Peter's recent mail on the
value of WS-Context context-by-value, to examine what would change in these
scenarios if the <ctx:context/> were to be replaced by a simple SOAP
header element. Strip out <ctx:context/>, replace the placeholder
"context state" with <protocol:context/>, place this element in the SOAP
header, and proceed. This would be a less restrictive, but I
believe legal, use of WS-I (i.e. move protocol-specific context info from
body to header).
It
would also be interesting to consider, in the light of Jim and Guy's
exchanges, what role activity completion plays, if any? Activity completion
can only be communicated to context recipients if they are registered with the
context service that knows that the activity is now complete. WS-Context does
not define such a registration-notification mechanism. This continues to leave
in question the independent value of WS-Context context-by-value. This type of
functionality must reside in the surrounding protocol (session,
coordination etc) that in my example is denoted by the namespace URI indicated
by the prefix "protocol" (the "referencing specification"). An example of such a
protocol is WS-CF, or in truncated form, WS-Coordination.
As
there is no bundle of contexts specified by WS-Context (if my understanding has
kept pace with the spec changes), the argument that value is provided by easing
interception (simpler to identify the group of contexts that must be processed
by a set of interceptors), becomes a non-argument.
Where
does this leave the independent value of WS-Context
context-by-value?
These
points are orthogonal to the issue: header element in the raw, body element in
the raw, or element embedded in an address.
Alastair
|
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]