Re: Synchronous Messaging Proposal - Some Thoughts

[Prasad Yendluri <pyendluri@webmethods.com>]

Dick,

Please see below in <PY>.

Prasad

Dick Brooks wrote:

Prasad,

>The synchronous response should accommodate only an acknowledgment message / response message. I don't see value in sending both (e.g. one followed by the >other in the HTTP body). The acknowledgment could come synchronously and a response later asynchronously.

Phase 1 of the TRP delivery matrix includes a use case depicting RPC like behavior (request/response), exemplified using a stock quote service.  I believe it's imperative for ebXML to support synchronous acknowledgements containing a business level response (as in the stock quote case).

<PY> Dick, 
we are not in conflict here. My statement is based on the general message
exchange model presented in http://lists.ebxml.org/archives/ebxml-transport/200011/msg00018.html,
where Acks could be different from responses with a business payload in
general.  In RPC like request/response type model, what you called 
"synchronous acknowledgements containing a
business level response", is same as 
the "response message" in my description. I was saying it does not make
sense to send the ack (w/o business payload) and the response (with business
payload) together (one followed by the other) in the same synchronous response,
as the response would constitute the ack here.
</PY>