$.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 object
$.ajax
The underlying call for all of the above
As for a tip on a "generic kind of jQuery parser", if you use
"getJSON" then there is nothing to parse, the returned object *will*
be a JSON object (as long as you properly crafted it on the server)
if you need a more configurable version of "getJSON", i wrote and use
this wrapper function
function reqJSON(url, params, success, error) {
var CallParams = {};
CallParams.type = params.Method || "POST";
CallParams.url = url;
CallParams.processData = true;
CallParams.data = params;
CallParams.dataType = "json";
CallParams.success = success;
if (error) {
CallParams.error = error;
}
$.ajax(CallParams);
}
and call it like so
var Params = {};
Params.SomeKey1 = "some value";
Params.SomeKey2 = "some value";
Params.Method = "GET"; // or "POST", which it defaults to
reqJSON(
"url of server page",
Params,
function(json) {
// if here, then "json" *is* a JSON object
},
function(x,y,z) {
// if here, then some error on server, "x" has the details
}
);
On Oct 13, 10:21 am, Alex Weber <[EMAIL PROTECTED]> wrote:
> first off, i dont get the difference between using $.ajax, $.post or
> $.get instead since the concept is the same afaik: you send a request
> and receive a response. the only difference in this case is that the
> response would be a JSON object... right?
>
> anyway... i've managed to generate tons of JSON objects of all sorts
> but haven't been able to come up with a decent parser thats not uber
> specific to each case...
>
> does anyone have any tips or a more generic kind of jQuery JSON parser
> and some help on how to put it all together?
>
> thanks!!
>
> -Alex
