2005/10/17
Dave points to his original piece on XML-RPC back in 1998. Item number 30 includes some, erm, interesting claims;
But RPC is important, no matter what format is used, because it allows choices
In allows choices by rejecting an architectural constraint which has been the foundational constraint of large scale, loosely coupled, distributed systems, since there’s been large scale, loosely coupled, distributed systems … for about 40 years now.
you can replace a component with another one
Ah, substitutability. Note that you can only replace an XML-RPC component with another one that has the same interface, at least if interoperability is important. Compare that to a system where every component has the same interface, where you can submit a document to any component for processing. Now that’s what I call substitutability.
no comment until now