Vidur, dist-app'ers:
At the last TBTF conference call, we discussed issue #44 [1], which arose out of our requirement 200 [2], and which was handed to the TBTF since request-response correlation comes within the scope of transport bindings and message exchange patterns. I took an AI to propose closing the issue as follows:
The TBTF has already defined a message exchange pattern [3] which provides for this type of correlation, and an instance of an HTTP binding [4] which expresses this feature natively in the underlying protocol. We have additionally described the fact that features [4] may be expressed either by binding specifications (either within or outside the purview of the underlying protocol itself) or by SOAP extensions (modules). Although we have not taken on this piece of work directly, we believe we have demonstrated it is possible to write a SOAP module specification which will implement the simple request-response feature via SOAP headers, and therefore provide a transport-neutral realization of the feature. We are confident that this work will occur, and that the results will likely end up in some form "blessed" by an appropriate standards group, however we will not normatively specify such an implementation in SOAP 1.2.
Is this sufficient? Opinions/comments on this would be greatly appreciated.
Thanks,
--Glen
[1] http://www.w3.org/2000/xp/Group/xmlp-issues.html#x44
[2] http://www.w3.org/TR/xmlp-reqs#z200
[3] http://www.w3.org/TR/2001/WD-soap12-part2-20011217/#singlereqrespmep
[4] http://www.w3.org/TR/2001/WD-soap12-part2-20011217/#soapinhttp
[5] http://www.w3.org/TR/2001/WD-soap12-part1-20011217/#transpbindframew