RE: Issues to think about in the MOM

Mark,

> > 3a. In effect, is an address that is used by a transport mechanism part 
> > of the message or not?
> 
> Yes, and I believe that holds for both application and transport
> protocols.  So not only is the URI to which a SOAP envelope is POSTed
> part of the message, but so are the IP and MAC addresses (at least in
> the HTTP/TCP/Ethernet case).

Which address are we talking about? Is it the address of the ultimate receiver? Is it the address of an intermediary as expressed in a SOAP header? Is it the address of an intermediary interposed by a transparent proxy (so that is actually different than the HTTP address itself)?

Ugo

> -----Original Message-----
> From: www-ws-arch-request@w3.org [mailto:www-ws-arch-request@w3.org]On
> Behalf Of Mark Baker
> Sent: Thursday, November 20, 2003 4:14 AM
> To: Frank McCabe
> Cc: www-ws-arch@w3.org
> Subject: Re: Issues to think about in the MOM
> 
> 
> 
> Hi Frank,
> 
> On Wed, Nov 19, 2003 at 10:17:30PM -0800, Frank McCabe wrote:
> > 3. The SOAP notion of an envelope is essentially the outer 
> wrapper of 
> > the message infoset.
> 
> SOAP 1.2 is unclear about this.  In some cases in the spec, that
> appears to be the case, but in others, it is not.  There's been
> discussions about this in the XMLP WG, e.g.
> 
> http://lists.w3.org/Archives/Public/xml-dist-app/2003Feb/thread.html#5
> 
> Also, the WSDL WG seems to just now be confronting this issue, e.g.
> 
> http://lists.w3.org/Archives/Public/www-ws-desc/2003Nov/0116.html
> 
> I've always maintained that the SOAP message is more than the SOAP
> envelope/infoset.  It just makes intuitive sense to me given how
> protocols are typically designed using layering & encapsulation.
> 
> So ...
> 
> > 3a. In effect, is an address that is used by a transport 
> mechanism part 
> > of the message or not?
> 
> Yes, and I believe that holds for both application and transport
> protocols.  So not only is the URI to which a SOAP envelope is POSTed
> part of the message, but so are the IP and MAC addresses (at least in
> the HTTP/TCP/Ethernet case).
> 
> FYI, this also relates to the group's issue #2;
> 
> http://www.w3.org/2002/ws/arch/2/issues/wsa-issues.html#x2
> 
> Mark.
> -- 
> Mark Baker.   Ottawa, Ontario, CANADA.        http://www.markbaker.ca
> 
>

Received on Thursday, 20 November 2003 12:27:56 UTC