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 🙂
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…