XML-RPC emerged in early 1998 it was published by UserLand Software and initially implemented in their Frontier product. With XML-RPC and web services, however, the Web becomes a collection of procedural connections where computers exchange information along tightly bound paths. XML-RPC has no notion of objects and no mechanism for including information that uses other XML vocabulary. XML-RPC parameters are a simple list of types and content - structs and arrays are the most complex types available. XML-RPC client specifies a procedure name and parameters in the XML request, and the server returns either a fault or a response in the XML response. XML-RPC uses a small XML vocabulary to describe the nature of requests and responses. XML-RPC uses the HTTP protocol to pass information from a client computer to a server computer. XML-RPC permits programs to make function or procedure calls across a network. XML-RPC is among the simplest and most foolproof web service approaches that makes it easy for computers to call procedures on other computers. These interfaces can be as simple as a single function call or as complex as a large API. Effectively, RPC gives developers a mechanism for defining interfaces that can be called over a network. RPC is a much older technology than the Web. As its name indicates, it is a mechanism to call a procedure or a function available on a remote computer.
0 Comments
Leave a Reply. |