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.
There’s a unique energy that comes with starting something new — a blend of excitement,…
As I continued work on BrainExpanded and its MCP service, I came to realize that…
Just over a month ago, I published "Playing with graphs and Neo4j". Back then, it…
After my initial implementation of some BrainExpanded-related ideas on top of dgraph using its GraphQL…
Say hello to the Graph Model Domain Specific Language (GMDSL), created with the help of…
As I wrote in previous posts, the manual recording of memories for BrainExpanded is just…