Overview ASP. net xml Web Services

ASP. net xml Web Service Infrastructure

The XML Web Service infrastructure is created based on the XML-based message communication that follows the published service description. Service description is an XML document written using the XML syntax of the WSDL language. It defines the XML Web Service Message format that can be understood by the XML Web Service. A service description acts as a protocol to define the behavior of an XML Web Service and instruct potential customers to interact with it. The behavior of the XML Web Service depends on the service definition and supported message types.

These modes indicate what the service user can expect when a message in the corresponding format is sent to the XML Web Service.

For example, the request/response mode associated with the Remote Procedure Call RPC) service defines which SOAP message mode is used to call a specific method. This mode also defines the format in which the response SOAP message will follow.

Another example of message mode is unilateral interaction. This mode is used when one-way communication occurs. In this case, the sender does not receive any messages, including fault messages, from the XML Web Service. The mode that defines the SOAP message format can be defined internally to describe the actual service. They can also be defined externally and imported into the service description.

In addition to the definition of the Message format and the message mode, the service description can also selectively contain the addresses of each XML Web Service endpoint. The format of this address corresponds to the protocol used to access the service, for example, the URL corresponds to HTTP or email address corresponds to SMTP Simple Mail Transfer Protocol ).

For more information about the WSDL specification, see W3C Web site http://www.w3.org/TR/wsdl ).

ASP. NETXML Web Service connection format

Binary protocols like DCOM are composed of a Method Request layer that removes the top of the proprietary communication protocol. Such a protocol is not helpful for creating universally available XML Web Services. This does not mean that you are prevented from using such protocols in the XML Web Service solution, but the disadvantage of using them is that such protocols rely on the specific structure of their underlying systems, this restricts the increase of potential customers.

Instead, you can construct XML Web Services to work together with one or more open protocols, just like the integrated use of HTTP and SOAP. As you expected, the infrastructure requires support for different protocols.

The XML Web Service is not limited to providing remote process call access. They can also be constructed to exchange structured information, such as purchase orders and invoices, and can also be used to automate and connect internal and external business processing.

HTTP-GET and HTTP-POST

HTTP-GET and HTTP-POST are standard protocol verbs that use HTTP to encode and transmit variable name/variable value pair parameters and use the relevant request semantics. Each HTTP-GET and HTTP-POST is composed of a series of HTTP request headers that define what the client has requested from the server, and the response is composed of a series of HTTP Response Headers and response data, if the request is successful, a response is returned.

The HTTP-GET Passes parameters in the format of urlencoded text that uses the MIME type application/x-www-form-urlencoded. Urlencoding is a character encoding that ensures that transmitted parameters are composed of compliant texts. For example, the encoding of a space is "% 20 ". The additional parameter can also be considered as a query string.

Like a HTTP-GET, HTTP-POST parameters are URL encoded. However, the variable name/variable value is not transmitted as part of the URL, but is transmitted within the actual HTTP request message. The above describes ASP. net xml Web Services.

1. DataList and Repeater controls of ASP. NET
2. Analysis of IIS ing in ASP. NET
3. Overview ASP. NET status types
4. Introduction to ASP. NET and Web servers
5. EnableViewState attribute of ASP. NET