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.
I am embarking on a side project that involves memory and multimodal understanding for an…
I was in Toronto, Canada. I'm on the flight back home now. The trip was…
The BBC article "How we fell out of love with voice assistants" by Katherine Latham…
Like so many others out there, I played a bit with ChatGPT. I noticed examples…