Refining Data Exchange Methodologies using JavaScript Object Notation

Authors

  • Yogesh Kumar Das B. Tech Computer Science Engineering, SRM University
  • Pulkit Jain B. Tech Computer Science Engineering, SRM University

Keywords:

JSON;AJAX;Data feed; Remote procedure call; serialization; deserialization; Asynchronous calling

Abstract

When designing an application that will communicate with a remote computer, a data format and exchange
protocol must be selected. There are a variety of open, standardized options, and the ideal choice depends on the
applications requirements and pre-existing functionality. For example, SOAP-based web services format the data in an
XML payload wrapped within a SOAP envelope.While XML works well for many application scenarios, it has some
drawbacks that make it less than ideal for others. One such space where XML is often less than ideal is with Ajax-style
web 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 is
created with JavaScript in a browser it's much easier to exchange data with something called JSON. JSON is an
acronym for JavaScript Object Notation. It is a sting-like notation that makes it easy to declare complex structures like
arrays and object.JSON is a data exchange format that was created from a subset of the literal object notation in
JavaScript.The charm of JSON is in its simplicity. A message formatted according to the JSON standard is composed of
a single top-level object or array. The array elements and object values can be objects, arrays, strings, numbers, Boolean
values (true and false), or null.

Published

2017-04-25

How to Cite

Yogesh Kumar Das, & Pulkit Jain. (2017). Refining Data Exchange Methodologies using JavaScript Object Notation. International Journal of Advance Engineering and Research Development (IJAERD), 4(4), 177–182. Retrieved from https://ijaerd.com/index.php/IJAERD/article/view/2485