in reply to Re^7: Are there any issues with JSON
in thread Are there any issues with JSON

Speaking of recommending JSON, over {...};

Any examples of JSON usage/in use, you (or anyone) would recommend. That I could draw from?

Thanks.

--Chris

¡λɐp ʇɑəɹ⅁ ɐ əʌɐɥ puɐ ʻꜱdləɥ ꜱᴉɥʇ ədoH

Replies are listed 'Best First'.
Re^9: Are there any issues with JSON
by Anonymous Monk on Jun 06, 2014 at 01:54 UTC

    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.

[reply]

      Well, that sounds encouraging. I can't believe I haven't looked this direction earlier.

      Thanks!

      ¡λɐp ʇɑəɹ⅁ ɐ əʌɐɥ puɐ ʻꜱdləɥ ꜱᴉɥʇ ədoH

[reply]
        Right, unvalidated data, that becomes an object you can call methods .... no no no no no no no no no no no :)
[reply]

In Section Seekers of Perl Wisdom