- From: <paul.downey@bt.com>
- Date: Mon, 17 Oct 2005 23:06:32 +0100
- To: <jmarsh@microsoft.com>, <concahill@aol.com>, <Tony.Rogers@ca.com>
- Cc: <dorchard@bea.com>, <john.kemp@nokia.com>, <mark.little@arjuna.com>, <markn@bea.com>, <public-ws-addressing@w3.org>
+1. A URI is an Identifier, which is not necessarily a Location. -----Original Message----- From: public-ws-addressing-request@w3.org on behalf of Jonathan Marsh Sent: Mon 10/17/2005 11:05 PM To: Conor P. Cahill; Rogers, Tony Cc: David Orchard; John Kemp; ext Mark Little; Mark Nottingham; WS-Addressing Subject: RE: Multiple Addresses in an EPR Conor wrote: > The spec currently requires that the physical > address be carried in a single wsa:Address element. The spec doesn't use the term "physical address". Or "logical address" for that matter. The WG had rather extensive discussions about this topic and had in the end to steer clear of defining wsa:Address as one or the other. AIUI, an implementation is free to use the value of the [address] property in the underlying transport (e.g. the HTTP address when using SOAP/HTTP), but is not required to do so. The client may instead route the message to a proxy, an intermediary, or perform a catalog lookup - all well-known infrastructure for delivering a message correctly to a final recipient. Each mechanism provides value-add to the message delivery path (security, robustness, better performance, etc.)
Received on Monday, 17 October 2005 22:09:00 UTC