> As far as I can tell, what we have, or at least what we want to have if
> we take this approach is SOAP-independent request-response. That is,
> something always goes out, something /always/ comes back, but neither
> message need be a SOAP envelope. The optionality is in the SOAPiness,
> not in the existence of a response.
That rules out true fire and forget, such as SOAP over UDP, right?
/r$
--
SOA Appliance Group
IBM Application Integration Middleware
* This address is going away; please use rsalz@us.ibm.com *