Start the. Net journey (1)

Source: http://www.dotnettoday.com/editorial/default.asp <br>
<Br>
At present, my main interest is to provide distributed computing through the web. From this perspective, I found that. NET has several exciting ideas: Web Services, SOAP/XML, and CLR (Common Language Runtime: general Language Runtime environment ). <Br>
<Br>
Web Service <br>
<Br>
Web services can be seen as remote process calls (RPC) scheduled by XML over HTTP ). I think. NET is basically a framework for creating, allocating, using, supporting Web Services, and providing a development environment for it. Web service promise: each application can appear as a service on the Internet. Web services will become a key technology because they are based on everyday use and proven mechanisms. <Br>
<Br>
HTTP transmission is a well-developed channel that works well even through the enterprise's firewall. SSL is widely used to provide HTTP security. Any language, component model, and operating system can use or provide Web Services. Take a look at the next generation of Visual Studio Tools, which promise to make it easier to create Web Services. <Br>
<Br>
SOAP <br>
<Br>
SOAP/XML is actually the lifeline of Web Services. It uses the common language XML and Protocol SOAP to describe the meaning of data. The world of distributed computing is filled with a lot of transactions and messages. When we use COM/DCOM, CORBA, and EJB for this purpose, today's Web applications rely heavily on manual skills, or use complex mechanisms to communicate between different technical camps. <Br>
<Br>
SOAP is indeed not the best solution for all applications. For example, if your applications require tight synchronization and coupling, you should always consider technologies like COM and RMI. <Br>
<Br>
HTTP is not the best-performing transmission protocol, and XML is also very lengthy, resulting in additional transmission load. In some cases, it is necessary to transfer pure binary data streams between applications more efficiently. However, if you can design an application into a Web service coupled with a loose asynchronous call, it will produce the benefits of easy integration, which makes the cost very worthwhile. <Br>
<Br>
The result is that as long as the soul language is XML, the service application does not need to know or care about the service pedigree.