Linked by Eugenia Loli-Queru on Wed 20th Feb 2002 18:45 UTC
A lot of people have trouble understanding what .NET really is and what its goals are. Mostly because Microsoft has done a good job of confusing everybody using terms that are not self-explanatory or with terms that mean more that one thing. This editorial will present my thoughts on .NET, what it really is, what its motivations and goals are, and why it is the next "big thing." Should we embrace it or fear it? Both, I daresay.
Permalink for comment
To read all comments associated with this story, please click here.
To read all comments associated with this story, please click here.
>Also, when using XML to describe how applications are supposed to talk to each other (through the web?), how does this relate to the .NET Framework and the CLR?
From the ArsTechnica article:
"One key feature of server application development is Web Services. A Web Services is a component running on a web server that is "consumed" (i.e., used) by a traditional client application, a web-based client application, or another Web Service. Web Services are consumed using Simple Object Access Protocol (SOAP), a remote procedure call mechanism using XML over HTTP, as their access protocol, in conjunction with WSDL (Web Service Description Language). WSDL is used to describe the interface(s) published on the web, so that consumers of the service know how to use it. SOAP is used during the actual execution of the consumer. The .NET library provides a number of classes to make this easy."
Do not misinterpret that the .NET applications are web pages, they are real applications.