Introduction to the use of XML Web Services in ASP. NET

To succeed in Network Diversity, XML Web Services must not care about the selected operating system, object model, or programming language. Moreover, XML Web Services of ASP. NET must be used to be as widely accepted as other Web-based technologies:

Loose coupling: if only the commands used can understand the self-described text-based messages mentioned above, the two systems are considered loose coupling. On the other hand, tightly coupled systems use a large number of customized software to enhance inter-system communication, and need to know more between systems.

Ubiquitous communication: individuals are unlikely to be able to construct an operating system, or will not integrate Internet access capabilities in the near future. Therefore, this requires a ubiquitous communication channel. Similarly, the ability to connect almost any system or device to the Internet will ensure that such systems and devices can be used by other systems or devices connected to the Internet.

General Data Format: by adopting existing open standards rather than dedicated Closed-Loop communication methods, any system can support the same open standards that can understand ASP. net xml Web Services. Using self-described text-based messages, XML Web Services and their customers can share these messages without having to know the composition of each underlying system, this will allow communication between completely different independent systems. XML Web Services use XML to implement this function.

ASP. net xml Web Services use a basic structure that provides the following functions: a discovery mechanism for locating XML Web Services; a service description for defining how to use these services; and the standard connection format used for communication.

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