1.HTTP's preferred protocol for web services, with 4 advantages: 1) HTTP is very simple, the request and response composition encoded in plain text (hypertext) is 2) HTTP is stateless. Once an HTTP request is sent, the connection information between the client and the server will be released, which is conducive to reducing the consumption of server resources. 3) HTTP's operating port 80, is an open 4) industry recognition in most firewalls. But HTTP's disadvantages: 1) Missing support for asynchronous messages 2) Unreliability of messaging
2. HTTP GET, POST, SOAP protocol is running on HTTP 1) GET: Request parameter is a sequence as a key / value pair (query string) is attached to the length of the query string on the URL is subject to a web browser And the limit of the web server (such as IE supports up to 2048 characters), is not suitable for transmitting large data sets, it is unsafe 2) POST: The request parameter is transmitted in a different portion of the HTTP title (named entity body), This part uses to transmit form information, so it must be set to: Application / X-WWW-FORM-URLENCODED. POST is designed to support user fields on a web form, and its parameters are also transmitted as Key / Value. However, it does not support complex data types because POST does not define semantics and rules for transferring data structures. 3) SOAP: It is a private version of HTTP POST, follows a special XML message format Content-Type set to: Text / XML can XML
3. .NET Web Service System Basic Structure 1) Design the web service as a .NET class, compile automatically create a WSDL document 2) Customer discovery to find Web services via UDDI discovery, decide to use 3) .NET automatically check the WSDL document, and generate A Customer Agent Class 4) Customer calling the web service method (actually a customer-proxy class --- web service communication) 5) The proxy class receives a SOAP reply, convert it to the appropriate .NET data type. Give customers
