W3C home > Mailing lists > Public > public-ws-addressing@w3.org > November 2004

RE: WS-A Issue 28 - Multiple ports needed in an EPR

From: Vinoski, Stephen <Steve.Vinoski@iona.com>
Date: Sat, 6 Nov 2004 23:51:01 -0500
Message-ID: <13AC4E67178F4D4EA31BB1BA645303130376FF@amereast-ems2.boston.amer.iona.com>
To: "Rich Salz" <rsalz@datapower.com>
Cc: "Sanjiva Weerawarana" <sanjiva@watson.ibm.com>, <public-ws-addressing@w3.org>

My apologies for being unclear. My answer had two parts: one about the target of a message, and the other about messages sent to a particular target where the messages contain addressing information about other (third party) services.

1. For the target, there's no requirement to always send the whole multi-address EPR with each message. This is because the target normally already knows the addresses by which it's reachable. There are cases, however, such as with routers that switch messages from one protocol/transport/format to another, that is made possible only by sending the whole multi-address EPR for the target. So sending the whole target EPR needn't be mandatory, but it should be allowed.

2. If you want to send an EPR for a third party service as part of a message to a target service, e.g., send a callback EPR to some event service to register for future notifications, then you need to send the whole EPR for the third party.

Hopefully that's clearer.

--steve

-----Original Message-----
From: Rich Salz [mailto:rsalz@datapower.com]
Sent: Saturday, November 06, 2004 11:25 PM
To: Vinoski, Stephen
Cc: Sanjiva Weerawarana; public-ws-addressing@w3.org
Subject: RE: WS-A Issue 28 - Multiple ports needed in an EPR


> Sanjiva is right. (I already answered this the previous time you asked
> it, Rich; see [1].)

I couldn't make sense of your answer.

Thanks.

-- 
Rich Salz                  Chief Security Architect
DataPower Technology       http://www.datapower.com
XS40 XML Security Gateway  http://www.datapower.com/products/xs40.html
XML Security Overview      http://www.datapower.com/xmldev/xmlsecurity.html
Received on Sunday, 7 November 2004 04:51:05 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 2 June 2009 18:34:59 GMT