While reading the 3rd part of the factored WS-Addressing spec, it occurred to me that the discussion on how to associate wsa:action headers with messages in WSDL operations or how to implicitly generate them could be simplified by having just a uniform action for all SOAP messages:
wsa:action="process:message"
Anything more in the action header may result into consumers making assumptions about the internal dispatching mechanics of the service (wsa:action as the new way to do RPC). Also, there may be a case that consumers will make assumptions about the semantics of the processing of the message based on the wsa:action header rather than the contents of the message body and the interaction protocol.
I really think that wsa:action should be left out š
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…
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…