Paper Details

When designing an application that will communicate with a remote computer, a data format and exchangeprotocol must be selected. There are a variety of open, standardized options, and the ideal choice depends on theapplications requirements and pre-existing functionality. For example, SOAP-based web services format the data in anXML payload wrapped within a SOAP envelope.While XML works well for many application scenarios, it has somedrawbacks that make it less than ideal for others. One such space where XML is often less than ideal is with Ajax-styleweb applications. While most browsers can construct, send, and parse XML, JavaScript Object Notation (or JSON)provides a standardized data exchange format that is better-suited for Ajax-style web applications.When the client iscreated with JavaScript in a browser it's much easier to exchange data with something called JSON. JSON is anacronym for JavaScript Object Notation. It is a sting-like notation that makes it easy to declare complex structures likearrays and object.JSON is a data exchange format that was created from a subset of the literal object notation inJavaScript.The charm of JSON is in its simplicity. A message formatted according to the JSON standard is composed ofa single top-level object or array. The array elements and object values can be objects, arrays, strings, numbers, Booleanvalues (true and false), or null.

Yogesh Kumar Das, Pulkit Jain, “Refining Data Exchange Methodologies using JavaScript Object Notation”, International Journal of Advance Engineering and Research Development (IJAERD), Vol. 4, Issue 4, pp. 177-182, April 2017.