Sorry for not following up... looks like I missed your response while I was away. However, I'm reasonably sure I don't understand. It doesn't seem like getJSON is supposed to wait... wraps with the callback function, and thus should run when there is a return. Can you give a bit more detail, or point me to an similar structure as what you describe?
Thanks! josh On Sat, Sep 6, 2008 at 8:36 AM, Rene Veerman <[EMAIL PROTECTED]> wrote: > don't wait for any response, just poll an array of 'open' responses and > handle whichever are ready? > > > On Thu, Sep 4, 2008 at 3:13 PM, Josh Rosenthal <[EMAIL PROTECTED]> wrote: > >> Hey all, >> I'm building a google map based application which allows users to query a >> number of different json returning data lookup services (ie: get Tax Parcel >> for this coordinate... get address, get USGS Quad Name, get Place Name). >> Each service is activated by clicking a different button, etc. While some >> of these queries run pretty fast, others (parcels), take ~ 30-40 seconds. >> Working in Firefox 3, I've found that once a user runs the slow getJSON, >> none of the other queries will run their callback, until that slow getJSON >> finishes. However, when I watch in firebug, I can see that we've actually >> queried and gotten a valid, wrapped response, and we're just waiting to >> process it. Basically, the jsonp calls may be asynchronous, but we get a >> bottleneck where we're waiting for the response to one jsonp call, but >> already get the answer to another, and yet have to wait til the first >> returns in order to do our second callback. >> >> IE7 appears to display more correct behaviour, with the callbacks firing >> in the order that responses are received. >> >> Any suggestions as to how to get FF3 to behave similarly? >> >> -Josh >> > >
