in reply to Are there any issues with JSON

Note that JSON is (at best) a transport format for structured data.

You haven't told us what parts of the Javascript bits in your CMS you want to replace, but I'm not really sure how moving to data can replace code unless you want to send commands from Perl to a generic Javascript driver that then acts on these commands.

The most important caveat with JSON is that it is implicitly UTF-8, so you will need to make sure that all your data processing is already UTF-8 before moving data through JSON to decouple the problems that UTF-8 brings from the other problems that your website change brings.

Replies are listed 'Best First'.
Re^2: Are there any issues with JSON
by taint (Chaplain) on Jun 03, 2014 at 12:54 UTC
    Ugh. I was on my out the door, and realized just that -- I didn't say what I was using it for. Sorry. :P

    My intention(s) are for HTML form "ques" -- you know, discription inside the element, feedback (inproper entry), and the likes. Also, I'll be building a custom editor with it (JSON).

    Once again, sorry. I know better than to ask a question like that. :(

    As to UTF-8; I wouldn't have it any other way. The day "Locale" vanishes, won't be a day too soon. As far as I'm concerned. :)

    --Chris

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

[reply]

In Section Seekers of Perl Wisdom