Putting the operation name in body of a SOAP message


Mark Baker
talks about the WSDL WG’s decision not to require the name of an operation in the body of a SOAP message. I personally think that this is good. Web Services are all about exchanging information and not identifying methods, operations, functions, procedures that must be called. What services do with the information they receive, through message exchanges, it’s up to those services. It’s all about not making any assumptions about the programming model or architecture at the other end.

Recent Posts

Reflecting on 2025: Building CVOYA’s Future with AI Coding Agents

As 2025 is now behind us, I wanted to share a few reflections from my…

2 days ago

DIY smart home accessory – It all started with a question to ChatGPT

Few months ago, we bought a sculpture from a local art fair for our Palm…

3 weeks ago

The Beginning of CVOYA

There’s a unique energy that comes with starting something new — a blend of excitement,…

3 months ago

Enhancements in Graph Model: Dynamic Entities & Full-Text Search

As I continued work on BrainExpanded and its MCP service, I came to realize that…

6 months ago

GraphModel: A .NET Abstraction for Graphs

Just over a month ago, I published "Playing with graphs and Neo4j". Back then, it…

7 months ago

Playing with graphs and neo4j

After my initial implementation of some BrainExpanded-related ideas on top of dgraph using its GraphQL…

8 months ago