I don't have time to go dig up examples from where I've used JSON but I wanted to tell you what I find to be the greatest virtue of JSON: cross-platform objects. Oh yeah, and the main reason people use it is that it's much less verbose than XML (less bandwidth).

If you pass JSON into javascript, it's trivial to inflate the object, add a prototype and "bang! it's an object with behaviors". Typically you would have methods that display, edit, whatever that data. When you're done, you pass the JSON core (data) back to your Perl server. On the Perl side, you can easily inflate the JSON to a hash and bless it into a class that provides persistence (or whatever). Well, anyhow, that's what I find awesome about JSON.

In reply to Re^9: Are there any issues with JSON by Anonymous Monk
in thread Are there any issues with JSON by taint

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.