Difference between revisions of "JSON"

From Organic Design wiki
(JSON-RPC)
m
Line 5: Line 5:
  
 
Besides using HTTP for transport, one may use TCP/IP sockets. Using sockets one can create much more responsive web applications with JSON-RPC, compared to polling data from a service with JSON-RPC over HTTP.
 
Besides using HTTP for transport, one may use TCP/IP sockets. Using sockets one can create much more responsive web applications with JSON-RPC, compared to polling data from a service with JSON-RPC over HTTP.
 +
 +
== JSONP ==
 +
''todo''
 +
 +
== JSON Schema ==
 +
''todo''
  
 
== See also ==
 
== See also ==

Revision as of 21:23, 15 September 2019

JSON (JavaScript Object Notation) is a lightweight data-interchange format. It is easy for humans to read and write. It is easy for machines to parse and generate. It is based on a subset of the JavaScript Programming Language, Standard ECMA-262 3rd Edition - December 1999. JSON is a text format that is completely language independent but uses conventions that are familiar to programmers of the C-family of languages, including C, C++, C#, Java, JavaScript, Perl, Python, and many others. These properties make JSON an ideal data-interchange language. (more...)

JSON-RPC

JSON-RPC is a remote procedure call protocol encoded in JSON. It is a very simple protocol (and very similar to XML-RPC), defining only a handful of data types and commands. In contrast to XML-RPC or SOAP, it allows for bidirectional communication between the service and the client, treating each more like peers and allowing peers to call one another or send notifications to one another. It also allows multiple calls to be sent to a peer which may be answered out of order.

Besides using HTTP for transport, one may use TCP/IP sockets. Using sockets one can create much more responsive web applications with JSON-RPC, compared to polling data from a service with JSON-RPC over HTTP.

JSONP

todo

JSON Schema

todo

See also