There has been more reaction on the ongoing discussion I mentioned in my last entry. Gudge is preparing a reply and Chris has some very interesting comments. However, I am choosing to highlight the following paragraph from Chris‘ entry for a different reason…
“The message exchange pattern (MEP) is just that; a pattern. The fact that many, if not most, people use SOAP in conjunction with a request/response MEP doesn’t preclude SOAP being used in the context of other, possibly more interesting and useful, MEPs.” (Chris Ferris, “None of the above”)
Me thinks… Wouldn’t it be really nice if we had a Web Services description language to capture these “interesting and useful MEPs” for SOAP message transfers? A vocabulary that didn’t promote request-response as the most interesting MEP but, instead, allowed us to describe complicated interactions? Just a thought 😉
Only few days now! 🙂
As 2025 is now behind us, I wanted to share a few reflections from my…
Few months ago, we bought a sculpture from a local art fair for our Palm…
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…