Re: [ws-caf] WS-Context 0.9.2 typo in wsctx.wsdl

[kevin.conner@arjuna.com]

> Do this error and the history mean the two operations sharing the same
> signature (TimeoutMessage and TimeoutSetMessage) have consistently been
> impossible to distinguish and the UserContextServicePortType is
> ambiguous?  Or, is the TimeoutSetMessage "just" unusable?  In other
> words, what is the severity of this problem?

In theory there is a potential for ambiguity if the implementation allows
concurrent message calls.

In practice, however, there will be a message id associated with the
request/response pairing and this could be used to distinguish which
response was received.

    Kev