I was using the API while toying around with some stuff and noticed that it seems the servers are caching some responses incorrectly due to use of JSONP. That is, if you request the partners feed:
You may get the right data, or you might get it wrapped in a function, ala jsonp. This come up as I was experimenting making calls both w/o and without the jsonp parameter (w/i a few seconds of each other). It was almost as if the server was remembering the function name I last passed in a similar json call, for example:
Worse, it seemed like a random round-robin as to what I'd get back. Sometime I'd get what I requested (or what I requested a few seconds ago) and other times I'd get something from another previous request. So it seemed like an issue of per-server caching on certain feeds that didn't take into account the jsonp param (or lack thereof). Thus, cache results differing at different times between different servers too.
Anyone else see this?
I was also trying the requests through YQL and it seemed like even the YQL servers where having trouble getting valid data back sometimes after I had requested some jsonp results (e.g., YQL backend also getting a jsonp wrapped response when it expected raw JSON).