Lao Li share: Web Services Architecture 2

Service Transport Layer

This layer is responsible for message transmission between applications. Currently, this layer includes Hypertext Transfer Protocol (HTTP), Simple Mail Transfer Protocol (SMTP), File Transfer Protocol (FTP), and some emerging protocols, such as the Block Extensible Switching Protocol (BEEP).

XML message Layer

This layer is responsible for encoding the message into a common XML format so that the message can be interpreted by the other end. Currently, this layer includes XML-RPC and SOAP.

Service Description Layer

This layer is responsible for describing the public interface as a specific Web service. Currently, the service description is handled through the Web Service Description Language (WSDL).

Service Discovery Layer

This layer is responsible for centralizing the service to a common registry and providing simple publishing/discovery capabilities. Currently, service discovery is handled through general description, discovery, and Integration (UDDI).
With the development of Web service, more layers may be added, and more technology can be added to each layer.
The following sections discuss the components of the Web service.

A little description of the service Transport layer

The bottom of the Web service protocol stack is the service Transport layer. This layer is responsible for the actual transmission of XML messages between the two computers.

Hypertext Transfer Protocol (HTTP)

HTTP is currently the most popular choice for service delivery. HTTP is simple, stable, and widely deployed. In addition, most firewalls allow HTTP traffic. This allows XML-RPC or SOAP messages to be impersonated as HTTP messages. This is great if you want to integrate remote applications, but it does bring a lot of security issues.

Block extensible Switching Protocol (BEEP)

This is a protocol that is expected to replace HTTP. BEEP is a new protocol that the Internet Engineering Task Force (IETF) is prepared to establish. The BEEP is built directly on the TCP layer and contains many built-in features, including an initial handshake protocol, authentication, security, and error handling. With BEEP, we can create new protocols for a variety of applications, including instant messaging, file transfer, content consolidation, and network management.
SOAP does not depend on any particular transport protocol. In fact, you can use SOAP through HTTP,SMTP, or FTP. Therefore, a promising idea is to use SOAP on top of BEEP.

Lao Li share: Web Services Architecture 2