I take issue with the assertion "where there are different protocols/transports/formats available for the same service, the "access to a Web service endpoint" requires the client to choose among alternatives". If I, the service, give you, the client, a single EPR then as far as you are concerned, there is only one mechansim with which you can communicate with me. So you don't need to make any choices ( except whether to communicate or not, I guess ). If I am available on multiple EPRs, then I'll provide you with multiple EPRs (perhaps in a WSDL document), *then* you have to choose one from the set. Gudge ________________________________ From: public-ws-addressing-request@w3.org [mailto:public-ws-addressing-request@w3.org] On Behalf Of Bergersen, Rebecca Sent: 04 November 2004 11:53 To: public-ws-addressing@w3.org Cc: Newcomer, Eric; Vinoski, Stephen; Bergersen, Rebecca Subject: WS-A Issue 28 - Multiple ports needed in an EPR Issue 28 - Multiple ports needed in an EPR According to the ws-addressing submission, "Endpoint references convey the information needed to identify/reference a Web service endpoint, and may be used in several different ways: endpoint references are suitable for conveying the information needed to access a Web service endpoint...." However, in the situation where there are different protocols/transports/formats available for the same service, the "access to a Web service endpoint" requires the client to choose among alternatives, each accessible in the standard manner through a port - but there are different ports for each protocol/transport/format alternative. When such alternatives exist, the EPR must be able to identify those multiple ports. Rebecca Bergersen Principal Architect, Middleware Standards rebecca.bergersen@iona.com <mailto:rebecca.bergersen@iona.com> ------------------------------------------------------- IONA Technologies 200 West Street Waltham, MA 02451 USA Tel: (781) 902-8265 Fax: (781) 902-8001 ------------------------------------------------------- Making Software Work Together TMReceived on Thursday, 4 November 2004 19:35:13 GMT
This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 2 June 2009 18:34:59 GMT