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 implication is that we don’t require lock-in to programmatic infrastructures to make data obtainable to Web-related platforms. JSON not only fits in properly with the Web’s JavaScript programming model, but it surely provides an easier, easier to grasp data model for Web programmers. Just as the Web, in a number of short years, has influenced nearly each aspect of our lives, from work, to play, to social interaction, so has XML, a universal knowledge description language, affected the distributed computing landscape. JSON is easier for these yearning for a easy data serialization format that works seamlessly with the Web.

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 … Read More