Translator Note: This is an article from MSDN to introduce the basic idea of Web services. I hope to give you some help from this article to understand the Web service thinking. This is the first translation of myself and published in 9CBS on 9CBS. There is a fallacy and translating improper is inevitable. I sincerely hope that everyone can make valuable comments and suggestions! Thank you!
Editor's note: This article provides developers to provide basic web service ideas. If you want to know about Web services and .NET, please refer to: http://www.microsoft.com/net/business.
Today, any way to construct distributed applications is not as fast as the Web model is faster and widely used. The great success of the web model is attributed to his core feature: the web model has a more loosely associated comparison of distributed programming models such as traditional RPC, DCOM and CORBA. The interaction of the web client and server is very simple, and they exchange information by transmitting MIME (Translator Note: Multi-Purpose Network Sports Extension Protocol), and can change the semantics of the information by modifying the protocol. The destination address of the information transfer is indirectly specified by the URL, which can be coordinated to coordinate load balancing, protocol tracking, and other functions. Due to the simplicity of interaction, the Web programming model enables system development that can use an increasing manner, unconfigured RPC and distributed object systems, and the applications must be developed at the same time. You can add client and server-side applications to web-based systems as needed, you can easily establish connections to new applications, and you can do this in a dispersion, except for the domain name server, not Need any centralized coordination and control. However, the system has depth interoperability, large-scale application capabilities and easy management. These are the web models that are fascinating. The basic idea behind the web service is to make the application also have loose connectivity for web distributed programming models, and these applications are not necessarily a browser as a web model. Web services provide a platform for establishing a distributed application that allows software running on different operating systems and different devices to develop software developed with different programming languages and software development tools of different vendors, all possible development and deployments. The software can use this platform to achieve distributed calculations.
How do Web services work?
The web service is built on the loose coupling characteristics of the traditional web programming model and uses this feature to other applications. Web services and traditional web use have three main differences: web services use SOAP messages instead of traditional web MIME messages; web services transfer protocols do not only adopt HTTP; web services provide information generation and metadata descriptions when using information. Below we discussed these three differences in detail: First, the web service communicates with SOAP messages. SOAP uses XML to pass data from a program to another, and SOAP defines the frame model of protocol conversion and extension, which can feed back error information and implement information on HTTP. SOAP's message contains any XML that the application needs to be sent. As shown in the following format: