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