3 ms·
I remember when XML was still young and I was introduced to XML-RPC. It was truly beautiful protocol -- straight forward, human readable, human writable, and e
by wvenable 16y ago
I remember when XML was still young and I was introduced to XML-RPC. It was truly beautiful protocol -- straight forward, human readable, human writable, and easy to implement. I wrote desktop apps that connected to web services written in different languages on different platforms and it all worked.
Then SOAP happened. The same philosophy as XML-RPC gone horribly wrong: a human readable format no longer readable by humans, insanely complex, and hard to implement properly (even with the libraries). Frustrating all around.
Although JSON is much simpler than XML, there's no reason why someone couldn't invent something as horrible as SOAP (or XSLT) on top of it. I can only hope that JSON implementers see the value of keeping things simple. Perhaps the existence of XML as an "enterprise" technology will help differentiate JSON in that way.
- roel_v 16y agoI used xmlrpc for this exact purpose (desktop to 'web service' - now there's a buzzword I haven;t heard in 5 years!) early this year, it was awesome. On the server side I had PHP's simple xml api, which also made pretty much all of the pain of parsing xml go away.