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 incre
I guess the main question here is how compares RPC with SOAP.
they both serve the same approach of communication abstraction by having stub objects you operate with and primitive/complex data types you get back without really knowing how this all is handled underneath.
I would always prefer (JSON-)RPC because
although there are reasons you should use SOAP, i.e. if you need naming parameters instead of relying on their correct order
some more details you get from this stackoverflow question