JSON vs. Rocky
4 January 2007There seems to be a big discussion lately about JSON vs. XML
- We all agree that the SOAP stack has gotten crazy
- JSON is thinner than Xml (slightly, no big deal really)
- JSON is native to the client. Having to load a specialized library to transform my data SUX.
- JSON can do cross domain calls that XmlHttp requests can not
- It is easier to encode / escape in JSON than XML
- JSON can define a function and data in one pass
- JSON can be used as a PUSH from the server (ok - it really is a managed pull, but at least it is not POLLING)
I thinks some people have been trying to revitalize Xml-RPC, which was killed off with the hype of SOAP. XmlRpc is kewl, but we have learned since then: we need a schema, a descriptor of services, binding, transactions, etc. Some of the recent work with JSON gives us these. Are they bound just to this ‘new’ technology? Of course not - but let us not launch a holy war.
No comments yet