one ui ajax 提交,javascript - UI unresponsive during AJAX calls - Stack Overflow

I've had similar problems working heavily with SharePoint web services - you often need to pull data from multiple sources to generate input for a single process.

To solve it I embedded this kind of functionality into my AJAX abstraction library. You can easily define a request which will trigger a set of handlers when complete. However each request can be defined with multiple http calls. Here's the component (and detailed documentation):

This simple example creates one request with three calls and then passes that information, in the call order, to a single handler:

// The handler function

function AddUp(Nums) { alert(Nums[1] + Nums[2] + Nums[3]) };

// Create the pool

myPool = DP_AJAX.createPool();

// Create the request

myRequest = DP_AJAX.createRequest(AddUp);

// Add the calls to the request

myRequest.addCall("GET", "http://www.mysite.com/Add.htm", [5,10]);

myRequest.addCall("GET", "http://www.mysite.com/Add.htm", [4,6]);

myRequest.addCall("GET", "http://www.mysite.com/Add.htm", [7,13]);

// Add the request to the pool

myPool.addRequest(myRequest);

Note that unlike many of the other solutions provided this method does not force single threading of the calls being made - each will still run as quickly (or as slowly) as the environment allows but the single handler will only be called when all are complete. It also supports the setting of timeout values and retry attempts if your service is a little flakey.

In your case you could make a single request (or group related requests - for example a quick "most needed" request and a longer-running "nice to have" request) to call all your data and display it all at the same time (or in chunks if multiple requests) when complete. You can also specifically set the number of background objects/threads to utilize which might help with your performance issues.

I've found it insanely useful (and incredibly simple to understand from a code perspective). No more chaining, no more counting calls and saving output. Just "set it and forget it".

Oh - concerning your lockups - are you, by any chance, testing this on a local development platform (running the requests against a server on the same machine as the browser)? If so it may simply be that the machine itself is working on your requests and not at all indicative of an actual browser issue.