Reliable XML Web Service (1)

Reliable XML Web Service
Eric Schmidt
Microsoft Corporation, XML Core Services Group, project manager
December 11, 2001
Download the sample code for this column.
Note: To download the code related to this article, you must:
Visual Studio. NET Release Candidate)
SQL Server 2000)
On PDC, I talked about reliable XML Web Service (Web Service). This topic is due to many conversations over the past year. Among the many common problems related to the creation of XML Web services, reliability is one of the five most important problems for developers to implement distributed Web services. This issue is not too difficult to separate, so this month I am going to talk about the tricky issue of building a reliable XML Web Service.
Overview
The most prominent aspect of Global XML Web Services Architecture (GXA [English]) is that the Architecture can be extended using the compositing processing protocol. These protocols are implemented through SOAP headers and provide a wide range of services including security, encryption, routing, and reliability. When you start to build a GXA-based application, you will find that GXA is essentially a message processing architecture that uses the standard encoding technology (SOAP) provides collaboration between systems and services. So far, most of the implementation work has been concentrated on the SOAP 1.1 and WSDL compatible services. Therefore, the Web service implementation solution can work with multiple languages and operating systems.
This is an amazing concept. Any two systems can communicate with each other as long as they can analyze XML and understand the SOAP specification rules. However, simple message exchange cannot meet the needs of complex business applications. Real applications (regardless of their internal domain architecture) require standardized services, such as security, authorization, and reliability at the message processing layer of Web services. There is a huge motivation behind the creation and implementation of Global XML Web Services Architecture (specifically SOAP, SOAP module and infrastructure protocol. With the release of four new specifications (WS-Routing, WS-Referral, WS-Licensing, and WS-Security) in March, we have begun to implement the next-generation XML Web Service. Despite the release of so many new specifications, there are still two areas with no public specifications, namely transaction processing and reliable message processing, mainly because these infrastructure protocols rely on the underlying SOAP module.