xml-rpc

What is the best Javascript XML-RPC client library in your opinion and why? I'am making a JQuery app and I need to communicate with my xmlrpc server with it. Found following libraries, but I have no idea what are their pros and cons: http://www.zentus.com/js/xmlrpc.js.html http://www.scottandrew.com/xml-rpc/ http://phpxmlrpc.sourceforge.net/jsxmlrpc/ http://www.vcdn.org/Public/XMLRPC/ http://mimic-xmlrpc.sourceforge.net/ There is a Google-hosted library here: http://code.google.com/p/json-xml-rpc/ . It supports both XML-RPC and JSON-RPC for JavaScript, and asynchronous as well as synchronous

Update: I have provided complete code example in answer below. I have built my own little custom XML-RPC server, and since I'd like to keep things simple, on both server and client side, what I would like to accomplish is to create a simplest possible client (in C# preferably) using WCF. Let's say that Contract for service exposed via XML-RPC is as follows: [ServiceContract] public interface IContract { [OperationContract(Action="Ping")] string Ping(); // server returns back string "Pong" [OperationContract(Action="Echo")] string Echo(string message); // server echoes back whatever message is

The arguments about the simplicity of solutions using XML-RPC or REST are easy to understand and hard to argue with. I have often also heard arguments that the increased overhead of SOAP may significantly impact used bandwidth and possibly even latency. I would like to see the results of a test that quantifies the impact. Any one know a good source for such information? Troy Alford There are a few studies which have been done regarding this which you might find informative. Please see the following: SO: Rest vs Soap Performance Q&A: SOAP and REST 101 Updated SQL Server Data Services: Northwind

I've never really understand why a web service implementer would choose one over the other. Is XML-RPC generally found in older systems? Any help in understanding this would be greatly appreciated. Christopher Mahan Differences? SOAP is more powerful, and is much preferred by software tool vendors (MSFT .NET, Java Enterprise edition, that sort of things). SOAP was for a long time (2001-2007ish) seen as the protocol of choice for SOA. xml-rpc not so much. REST is the new SOA darling, although it's not a protocol. SOAP is more verbose, but more capable. SOAP is not supported in some of the older

"Does distributed computing have to be any harder than this? I don't think so." -- Byte . “进行分布式计算需要了解比他本身还要多？我想不是这样。” —Byte. What is XML-RPC? It's a spec and a set of implementations that allow software running on disparate operating systems, running in different environments to make procedure calls over the Internet. 他是一个规范和实现的集合，允许软件在异构系统中运行，运行在不同的环境中的程序通过Internet实现过程调用。 It's remote procedure calling using HTTP as the transport and XML as the encoding. XML-RPC is designed to be as simple as possible, while allowing complex data structures to be transmitted, processed and returned.

XML-RPC vs. SOAP by kate rhodes masukomi@masukomi.org A simple guide to choosing the best protocol for your XML Remote Procedure Call needs. Within the world of XML there are two main ways to implement a Remote Procedure Call (RPC). XML-RPC and SOAP. This document will explore the differences between these two methods in order to help you decide which is best suited to your needs. General information XML-RPC http://www.xmlrpc.com XML-RPC is "...a spec ( http://www.xmlrpc.com/spec ) and a set of implementations that allow software running on disparate operating systems, running in different