erp-soap 概况（ERP的肥皂概况）.docVIP

erp-soap 概况（ERP的肥皂概况） This article is contributed by Liu and Inner Mongolia DOC documents may experience poor browsing on the WAP side. It is recommended that you first select TXT, or download the source file to the local view. OAPOAP- profile SOAP: Simple Object Access Protocol SOAP (SOAP:Simple, Object, Access, Protocol) Simple object access protocol (SOAP) is a lightweight, simple, XML based protocol designed to exchange structured and solidified information on WEB. SOAP can be used in conjunction with many existing Internet protocols and formats, including Hypertext Transfer Protocol (HTTP), simple mail transfer protocol (SMTP), and Multipurpose Internet mail extension protocol (MIME). It also supports a large number of applications from messaging systems to remote procedure calls (RPC). The SOAP consists of three parts: SOAP package: it defines a framework that describes what is in the message, who should handle it, and whether it is optional or necessary. SOAP encoding rules: it defines a serialization mechanism for exchanging instances of data types defined by an application. SOAP RPC says: it defines protocols for representing remote procedure calls and responses. SOAP messages are basically one-way transmissions from the sending end to the receiving end, but they often combine to execute patterns like request / reply. All SOAP messages are encoded using XML. A SOAP message is an XML document that contains a necessary SOAP package, an optional SOAP header, and a required SOAP body block. Binding SOAP to HTTP provides the advantages of utilizing both SOAP style and distributed flexibility as well as the advantages of HTTPs rich feature library. Sending SOAP over HTTP does not mean that SOAP overrides existing HTTP semantics, but rather that the SOAP semantics on HTTP maps naturally to the HTTP semantics. In the case where HTTP is used as the protocol binding, the RPC request maps to the HTTP request, while the RPC response maps to the HTTP response. However,