I've been running into a problem querying GData (Google's Data APIs)
using jQuery and JSON. jQuery's ajax function automatically adds a
cache-buster timestamp to the query, and Google is barfing on it.
The timestamp is inserted starting around line 2608 in jQuery 1.2.3.
As an example, here is
I've had issues where jQuery's JSON requests were treated as XHRs if
there was no JSONp callback. That obviously doesn't work going cross-
domain.
If you change your url to /http://stufftolet.com/test/usercontacts.js?
callback=? it should work, though you're going to need to hook up the
result.
There are a problems requesting JSON object from GDATA using jQuery.
jQuery appends a timestamp to the url which causes GData to throw an
Invalid parameter error. If you check with FireBug, you'll see it.
Also, GData's API says to use alt=json-in-script instead of just
alt=json. It's hard to
This is a bit of an odd request, but maybe there's something simple
I'm overlooking.
I have a function which pulls JSON data from Google's GData service.
Normally this works pretty well, save a bug or two on Google's end.
The problem is that errors are served as a plain text string without a
4 matches
Mail list logo
