Comments on: JSONP, Quickly

By: Beta version of the HathiTrust Volumes API available » Robot Librarian

Beta version of the HathiTrust Volumes API available » Robot Librarian — Tue, 15 Dec 2009 20:10:49 +0000

[...] JSONP output is supported — just throw a ‘&callback=blahblahblah’ on the end of the URL you call and you’ll get a function definition back. [...]

By: Julian

Julian — Fri, 06 Nov 2009 07:29:13 +0000

I’d recommend $.jsonp rather than $.getJSON or $.ajax. It’s more suited for jsonp than jQuery’s current implementation.

http://code.google.com/p/jquery-jsonp/

By: Nir

Nir — Thu, 07 May 2009 15:18:58 +0000

That’s definitely the better way – JSONP is really temporary solution until client/server support for cross-origin requests is more widespread.

By: Top Posts « WordPress.com

Top Posts « WordPress.com — Thu, 07 May 2009 00:20:49 +0000

[...] JSONP, Quickly I discovered JSONP just recently, following Chris‘ comment. Though I initially didn’t intend to support [...] [...]

By: Elijah Grey

Elijah Grey — Wed, 06 May 2009 20:17:47 +0000

Not all third-party JavaScript has to be unsafe, as shown in my comment below.

By: Elijah Grey

Elijah Grey — Wed, 06 May 2009 20:17:00 +0000

JSONP is very unsafe for XDM. I would rather use either cross-domain XMLHttpRequest, XDomainRequest, or pmxdr

By: Nir

Nir — Wed, 06 May 2009 15:39:57 +0000

Thanks Josh! You’re right about security issues, of course.

By: Josh Peters

Josh Peters — Wed, 06 May 2009 11:39:47 +0000

What you call JSONP has been a standard practice at YAHOO! for some time.

http://developer.yahoo.com/common/json.html

One needs to be cautious with this sort of usage though, as you’re essentially trusting a third party to provide you with code. Even if you’re the author of the proxy you could easily suffer from man-in-the-middle attacks if someone can intercept and send you more malicious code.

Of course, that’s true of all third-party linked javascript.