Why Do We Need Another Xml-rpc Implementation (specifically Xmlrpc++)

1.	Why Do We Need Another Xml-rpc Implementation (specifically Xmlrpc++)?
Answer» XmlRpc++ is DESIGNED to make it easy to incorporate XML-RPC client and server support into C++ applications. It is written in portable, extendable C++. No other libraries are required, other than your SYSTEM's socket libraries. Simple XML parsing and HTTP support are BUILT in. It is easy to build and has a SMALL API. There is no easier WAY to add remote procedure call support to a C++ application that I know of. XmlRpc++ is designed to make it easy to incorporate XML-RPC client and server support into C++ applications. It is written in portable, extendable C++. No other libraries are required, other than your system's socket libraries. Simple XML parsing and HTTP support are built in. It is easy to build and has a small API. There is no easier way to add remote procedure call support to a C++ application that I know of.

Why Do We Need Another Xml-rpc Implementation (specifically Xmlrpc++)?

Answer»

XmlRpc++ is DESIGNED to make it easy to incorporate XML-RPC client and server support into C++ applications. It is written in portable, extendable C++. No other libraries are required, other than your SYSTEM's socket libraries. Simple XML parsing and HTTP support are BUILT in. It is easy to build and has a SMALL API. There is no easier WAY to add remote procedure call support to a C++ application that I know of.

XmlRpc++ is designed to make it easy to incorporate XML-RPC client and server support into C++ applications. It is written in portable, extendable C++. No other libraries are required, other than your system's socket libraries. Simple XML parsing and HTTP support are built in. It is easy to build and has a small API. There is no easier way to add remote procedure call support to a C++ application that I know of.

Discussion

No Comment Found

Related InterviewSolutions

How Do I Send Cookies With A Request?
How Do I Supply Authentication Credentials?
What If The Xml-rpc Method Name Is Not Valid In My Programming Language?
How Are Xml-rpc Arrays Represented As .net Types?
What If The Xml-rpc Struct Member Name Is Not Valid In .net?
How Does Xml-rpc.net Represent Xml-rpc Requests And Responses?
How Do You Use Xmlrpc++ As An Xml-rpc Server?
What Is An Xml-rpc Server (client)?
Why Not Use Soap (or Dce Rpc, Onc Rpc, Corba, Dcom, ...)?
Why Do We Need Another Xml-rpc Implementation (specifically Xmlrpc++)?