- From: <michael.mahan@nokia.com>
- Date: Fri, 26 Sep 2003 11:59:25 -0400
- To: <UCorda@SeeBeyond.com>, <jean-jacques.moreau@crf.canon.fr>
- Cc: <www-ws-arch@w3.org>
It seems that WS-Routing explicitly describes a message path through intermediaries, whereas WS-Addressing does not. Or perhaps I misread the spec. Could a WS-Addressing expert out there weigh in on its role and capabilites. Thx, MikeM >-----Original Message----- >From: ext Ugo Corda [mailto:UCorda@SeeBeyond.com] >Sent: September 26, 2003 11:33 AM >To: Jean-Jacques Moreau; Mahan Michael (NRC/Boston) >Cc: www-ws-arch@w3.org >Subject: RE: Intermediary Text > > > >> > - Router. A Web service message can follow a particular >> "path" through >> > an arbitrary number of intermediaries where each Web service >> > intermediaries would provide a value-added services to the message >> > and hence to the application. Note that for a request-response MEP, >> > the message may traverse through different intermediaries on it >> > request and response paths. Routing intermediaries could belong to >> > the trust domain of the requester, the provider, or some >> third party. >> >> Maybe add a link to WS-Routing? > >Or to WS-Addressing. (My understanding is that WS-Addressing >has made WS-Routing obsolete). > >Ugo > >
Received on Friday, 26 September 2003 12:02:28 UTC