true :)
short of encrypting the hell outta all my responses and then decrypting them
client-side there's nothing to do really..
and even in that case since the decryption is done client-side the algorithm
would be easily accessible :P
i guess just try not to pass sensitive information and also mi
Any security you feel like you get from JSON or CSV is flat out naive
Either one is just as insecure as plain ol text
The advantage of using the $.getJSON method (which remember, is just
$.ajax but with the dataType set to "json") is that you don't need to
do anything special to parse it whe
Thanks Mickster and MorningZ! :)
Gonna read up on those articles and functions tonight and give it a
shot! :)
I know its terrible practice but laziness always made me return AJAX
requests as CSV strings that i'd then explode and access the array's
indices (since i know in what order the values c
$.post
gets some data, puts the outgoing data in the header, data comes back
as whatever
$.get
gets some data, but puts the outgoing data on the querystring, data
comes back as whatever
$.getJSON
gets some data, using "get" by default, data comes back and jQuery
*expects* it to be a JSON obje
Hi Alex,
maybe this tutorial can give you a start:
http://www.prodevtips.com/2008/08/15/jquery-json-with-php-json_encode-and-json_decode/
Personally, I use the script from here:
http://www.json.org/js.html
But I don't think you really need an extra parser - $.getJSON should
already parse the re
5 matches
Mail list logo
