- From: Ugo Corda <UCorda@SeeBeyond.com>
- Date: Thu, 20 Nov 2003 12:17:23 -0800
- To: "Mark Baker" <distobj@acm.org>
- Cc: <www-ws-arch@w3.org>
Regarding the unclear cases 7 and 8: 7. WSDL-based extensions The way I understand this case (again, I was not the author of the original list) is a WSDL (non-standard) extension that would describe routing information not expressed at the WSDL message level itself. The submitter would just look at that information and exploit whatever out-of-band mechanism is available (at any level of the transmission stack) to realize the described routing. I don't have any specific example of this, and in fact I think it was raised as a (in principle possible) speculation. 8. Using application-specific semantics I think this is just the case where routing info is expressed at the level of the application payload (no SOAP feature/module involved). Ugo > -----Original Message----- > From: Mark Baker [mailto:distobj@acm.org] > Sent: Thursday, November 20, 2003 11:52 AM > To: Ugo Corda > Cc: www-ws-arch@w3.org > Subject: Re: Issues to think about in the MOM > > > On Thu, Nov 20, 2003 at 10:50:49AM -0800, Ugo Corda wrote: > > > Yes, I agree, but that address isn't part of the message. > > > > Could you please clarify which types of addresses are part > of a message and which ones are not? Given the following list > of possible intermediary addressing mechanisms, which ones of > the associated addresses do you think are part of the message: > > > > 1. IP address interception (e.g., "transparent proxies") > > Not part of the message. > > > 2. DNS address interception/redirection (e.g., Akamai, > "virtual hosting") > > Not part of the message. > > > 3. HTTP proxy configuration (and autoconfiguration...) > > Part of the message. > > > 4. IP routing interception (e.g., firewalls) > > You mean NAT? If so, not part of the message. > > If not NAT, then it is part of the message. > > > 5. HTTP redirection (Status code 30x) > > Well, that's not technically an intermediary scenario, as the redirect > is a result of the message reaching the ultimate receiver. > But the URI > of the resource producing the redirect is part of the > message, if that's > what you mean. > > > 6. SOAP routing / redirection (e.g., WS-Routing, WS-Addressing) > > Part of the message. > > > 7. WSDL-based extensions > > 8. Using application-specific semantics > > Don't know what you mean. > > Mark. >
Received on Thursday, 20 November 2003 15:18:56 UTC