Arvola,
My, you're a quick reader...
You're understanding covers the flag's semantics as it appeared in the 1.08
document. Maintaining the existing "keep channel open 'til a response is
ready" semantics, we slightly expanded the feature to include making sure an
intermediate SOAP processor doesn't close the connection. In essence, we
recognised the possibility of "regular" SOAP nodes linking full-blown MSH
nodes.
The previous synchronous mode would have supported MSH -> HTTP proxy -> MSH
because HTTP proxies operate in a synchronous mode by default. The new flag
allows MSH -> SOAP -> MSH in spite of the asynchronous mode the SOAP node
might prefer.
You're correct that the previous flag in QoS is no longer necessary.
We discussed placement of this module's description in our document during
the meeting and the consensus seemed to be putting this feature in the base
section because it may apply even to a SOAP node with just a bit of ebXML
smarts -- level 0 in ebXML conformance.
thanx,
doug