March 17, 2011, 6:24 p.m.
posted by angryuser
Roadmap to ASP.NET Web Services
Two major features in .NET are the ability to create XML Web Services Servers and XML Web Services Clients. There are also several related APIs (application programming interfaces) for manipulating DISCO (Web Services Discovery Language) and WSDL (Web Services Description Language) documents.
The engine that drives most of these features is XML Serialization. This API, found within the System.Xml.Serialization namespace, provides the ability to read and write XML without a DOM (Document Object Model) class or an XML-based stream reader. Instead, classes can be mapped to schema-based XML using a default set of rules, plus a variety of optional attributes to customize this serialization. Chapter 5, XML Serialization with .NET, discusses XML Serialization technology.
In addition to XML Serialization, the server-side infrastructure is based on ASP.NET. This provides for easy integration with several ASP.NET features, such as process restarting and caching. It also facilitates use of the Session, Application, and other intrinsic objects with ASP.NET. These intrinsic objects enable Web authors to store per-user and per-application state, as well as to interact with the underling HTTP transport more closely. Technically speaking, the server-side architecture is implemented with an ASP.NET Handler.
On the client side, the transport technologies of System.Net transport SOAP messages that are packaged together with the client-side infrastructure and XML Serialization. Client access is accomplished via custom proxy classes that use the WebRequest and HttpWebRequest classes. Any kind of .NET application can use these proxy classes: a Windows form, a Web form, or even another Web service.