This post originated from an RSS feed registered with .NET Buzz by Christian Weyer. Original Post: Messaging, XML, SOAP and asynchronous processing Feed Title: Christian Weyer: Web Services & .NET Feed URL: http://www.asp.net/err404.htm?aspxerrorpath=/cweyer/Rss.aspx Feed Description: Philosophizing about and criticizing the brave new world ... Latest .NET Buzz Posts Latest .NET Buzz Posts by Christian Weyer Latest Posts From Christian Weyer: Web Services & .NET

Thanks my friend. I really owe you beer at PDC. While a lot of people seem to not find enough time to write up their inner thoughts and feelings about all the SOAP and Web services misconception in just a few words (including me :-(), Ingo did that for all of us:

SOAP is not a Remote Procedure Call
Web Services ... that's Remote Procedure Calls (RPC) via HTTP and SOAP, right? Somehow the successor to DCOM and other remote procedure call frameworks, true? In this article, I discuss common misconceptions like these along with explaining why using only [WebMethods] deprives you of some of the most important features of XML Web Services: XML and Messaging. This article will show you how you can get back to XML and messages, and will change the way you think about Web Services. Forever.

The Flowchart Lie
Most application architects and developers tend to implement business processes using synchronous request/response interactions. This article discusses the reasons and drawbacks of this approach, and shows why and how asynchronous business process could be implemented using asynchronous messaging

Finally, someone spoke a word ...

Note to self: Why the hell didn't I write my piece for a column in German dotnetpro magazine in English, beef it up with some code snippets and post it on my weblog? We will never know ... but it is about this very topic: Web Services and SOAP is not RPC!