Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>Neither are protocols...</p> <p><strong>XML</strong></p> <pre><code>XML stands for eXtensible Markup Language. </code></pre> <p>Ref: <a href="http://www.w3schools.com/xml/" rel="nofollow">http://www.w3schools.com/xml/</a></p> <p><strong>JSON</strong></p> <blockquote> <p>JSON: JavaScript Object Notation.</p> <p>JSON is syntax for storing and exchanging text information. Much like XML.</p> <p>JSON is smaller than XML, and faster and easier to parse.</p> </blockquote> <p><a href="http://www.w3schools.com/json/" rel="nofollow">http://www.w3schools.com/json/</a></p> <p>So based on the title of your question I would choose neither. However that is me being pedantic.</p> <p>So it is <em>your</em> platform, and it is good to see you trying to apply standards we know and love. Why not give us a choice by offering both? You are controlling the way the data is sent back so allow the client to specify a preferred language and then if it does not choose one or the other.</p> <p>The Windows Communication Foundation does this well and makes the developer's life much easier. A good tutorial on this can be found at <a href="http://www.codeproject.com/Articles/105273/Create-RESTful-WCF-Service-API-Step-By-Step-Guide" rel="nofollow">http://www.codeproject.com/Articles/105273/Create-RESTful-WCF-Service-API-Step-By-Step-Guide</a> where both JSON and XML are offered.</p> <p>If you aren't using .Net then there are similar setups on different platforms. The bottom line is that once you have gathered your data to return, you should be able to send it to either an XML or JSON output which will then serialize and send it.</p> <p>If you want an <em>opinion</em> I prefer JSON as it can be easier to transform back into an object on lots of platforms. Also due to its nature it has a smaller footprint. For .Net there is the <a href="http://json.codeplex.com/" rel="nofollow">JSON .Net</a> library and on Java there's <a href="http://code.google.com/p/google-gson/" rel="nofollow">Google's GSON</a>, both make life easier for the developer however there are equivalents for XML.</p>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload