[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: New issue: Scope of MakeConnection is unconstrained
The spec says “This specification places no constraint
on the types of messages that can be returned on the transport-specific
back-channel.” This allows any message whatsoever to be returned in
response to a MakeConnection. This flexibility complexity complicates the
job of the RM Destination, as it will need to expect messages that have nothing
to do with RM coming back on the response to a MakeConnection. To simplify the job of the RM destination and to ensure
maximum interoperability on MakeConnection, the types of messages allowed as a
response to a MakeConnection message should be constrained to messages with RM
namespaced elements in the body, or in a header. Interoperable behavior
(e.g. ignoring such messages or
surfacing a fault) should be defined for messages that aren’t related to
a reliable conversation. |
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]