This Web Service article series covers all the important standards within the Web Services stack and ties them along with real-world examples. If you mean it’s easier to have a single data interchange format instead of two, that’s incontrovertibly the case. Recently just a few XML consultants have been claiming that the choice made by massive Web Service suppliers, like Twitter and Foursquare, to drop XML from their Web Services infrastructure shouldn’t be very attention-grabbing information. XML is pure knowledge description, not tied to any programming language, working system or transport protocol. We have also lately dropped XML assist for all of our hottest Web Services for many of the causes mentioned by Twitter and Foursquare.
The architectural revolution surrounding XML is mirrored in a move from tightly coupled methods primarily based on established infrastructures comparable to CORBA, RMI and DCOM, each with their very own transport protocol, to loosely coupled systems riding atop customary Web protocols reminiscent of TCP/IP.
This is what those who do not perceive the massive fuss over JSON should take be aware and realize: Where good developers can simplify, they do – and in the case of JSON vs. XML, XML finally ends up on the chopping block in many know-how firms lately.