WSSOA英文版培訓课件PPT第课SOAP.pptVIP

BUPTSSE SOA principles practice Lecture 4 SOAP Agenda Background and historical perspective What is SOAP? Structure of a SOAP message Message Processing Mapping SOAP to a transport protocol Using SOAP to extend existing services Limitations of SOAP Alternative architectures for messaging Background and historical perspective Network Programming Builds on top of networking protocols (primarily: UDP, TCP, HTTP) – Lowest-level API just provides user-level abstractions for TCP and UDP Sockets: Application-level end-point of communication Remote Procedure Calls (RPC) Writing distributed applications using the Sockets API is complicated – Program needs to explicitly send/receive messages – Violates programming transparency RPC: Remote Procedure Call ? Original goal: Provide complete programming transparency – Interaction with “procedures” on remote hosts as if they were local – However, needed to deal with several issues ? Different memory spaces, Parameter passing, Binding, Failures Now: A higher-level abstraction for distributed programming – Provides near-transparency RPC History Original idea described in a 1983 paper by A. Birell and B. J. Nelson Several implementations – Xerox – SunRPC: widely used (NFS) – DCE: is the Distributed Computing Environment, from the Open Software Foundation – DCE(OpenGroup): basis for Microsoft’s implementation of RPC in COM – … – XML-RPC ? same underlying ideas, but leverages web standards Overall Structure of RPC Client process blocks for duration of the call – Just like in a local procedure call – Asynchronous RPC: early reply from server RPC package is at the session layer – Can work with different transports Shared Memory, UDP or TCP has to be specified at setup time Message passing completely hidden from programmer Understanding RPC: Client and Server Stubs We want to make RPC’s look like local procedure calls Client stubs allow callers to make remote calls that look like local calls Server stubs allow callees to re