> What you are describing is the use of a synchronous protocol (HTTP) to > synchronously transfer the state (you know it was received) for asynchronous > processing (later). > > I assume that later on you will receive a message indicating whether the > request was processed. So at the higher-level (say choreography) the > interaction involving request/response is synchronous, but each individual > operation is consider asynchronous, yet using a synchronous protocol to > ensure receipt. I understand your explanation, but I don't think this advances the effort, because the meaning of "synchronous protocol" is not clear, at least not to me. WaldenReceived on Monday, 24 February 2003 15:14:14 GMT
This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 3 July 2007 12:25:15 GMT