- From: David Orchard <dorchard@bea.com>
- Date: Thu, 2 Mar 2006 07:22:45 -0800
- To: "Richard Salz" <rsalz@us.ibm.com>, "Mark Baker" <distobj@acm.org>
- Cc: <public-ws-addressing@w3.org>, <public-ws-addressing-request@w3.org>
How can you "know"? 202 says you can't know. And how can you preclude the response being "the" soap response? We are dealing with soap 1.1 which has no sense of MEPs. All we can talk about in a SOAP binding is the constructs that soap 1.1 gives us. WS-A goes on top and says if you are doing request-response using non-anonymous aka 2 different http connections, then the response must be on a separate http connection. I think that is the right layering of dealing with "responses". >From the very latest ws-a soap binding spec: When "http://www.w3.org/2005/08/addressing/anonymous" is not specified for the response endpoint, then the message SHOULD be part of a binding that supports not returning a SOAP envelope in the HTTP response. Any response message SHOULD be sent using a separate connection and using the address value specified by response endpoint. Cheers, Dave > -----Original Message----- > From: Richard Salz [mailto:rsalz@us.ibm.com] > Sent: Thursday, March 02, 2006 4:05 PM > To: Mark Baker > Cc: David Orchard; public-ws-addressing@w3.org; public-ws-addressing- > request@w3.org > Subject: Re: SOAP 1.1 request-optional-response http binding > > I agree with Mark. I need to know deterministically if the response- body > is "the" SOAP message or not. MAY is definitely the wrong thing here. > > /r$ > > -- > SOA Appliance Group > IBM Application Integration Middleware _______________________________________________________________________ Notice: This email message, together with any attachments, may contain information of BEA Systems, Inc., its subsidiaries and affiliated entities, that may be confidential, proprietary, copyrighted and/or legally privileged, and is intended solely for the use of the individual or entity named in this message. If you are not the intended recipient, and have received this message in error, please immediately return this by email and then delete it.
Received on Thursday, 2 March 2006 15:24:33 UTC