2011/1/4 Michael Dale<mdale(a)wikimedia.org>rg>:
It may hurt caching to serve everything over
jsonp since we can't set
smaxage with callback=randomString urls. If its just for editing its
not a big deal, untill some IE svg viewer hack starts getting all svg
over jsonp ;) ... Would be best if we could access this data without
varying urls.
Yes, JSONP is bad for caching.
Well, if the response is informative enough, you can often use constant
callback names. A lot of my scripts which use the API do that. Of
course, it may mean a bit more work if you're using a framework like
jQuery which defaults to random callback names, but it's not that much.
A couple of examples off the top of my head: