In addition to defining addressing-related information headers for SOAP messages, WS-Addressing introduces the concept of an EndpointReference (EPR) which is used as the means of capturing the addressing-related information of a service endpoint. I don’t see why an EPR couldn’t be of the form:
<wsa:ReplyTo>
<!- Protocol-specific addresses ->
<wsa:Address>http://service.com/myservice</wsa:Address>
<wsa:Address>corba:bla-bla-bla</wsa:Address>
<wsa:Address>tcp-ip:123.123.123.123</wsa:Address>
<!- And a logical address ->
<wsa:Address>urn:my:service</wsa:Address>
</wsa:ReplyTo>
If a service wishes to make available EPRs that advertise the service’s accessibility over a number of transports, why shouldn’t we allow it to? So, I agree with Steve‘s arguments on this one.
The alternative, of course, is to have separate EPRs for each of the above <wsa:Address>
elements.
As I wrote in previous posts, the manual recording of memories for BrainExpanded is just…
Imagine a world where your memory is enhanced by a team of intelligent agents, working…
As part of the BrainExpanded project, I’m building an iOS app that lets users easily…
Artificial Intelligence (AI) has rapidly evolved over the past few decades, becoming an integral part…
Happy New Year everyone! I was planning for my next BrainExpanded post to be a…
See "BrainExpanded - Introduction" for context on this post. Notes and links Over the years,…