looking or suggestions on understanding ajax asyncronous issues
I will make a series of ajax calls on my page. The first one calls a php script that will run for a very long time on the server.
While it is running, I call other php pages via ajax to do other things. All calls are being held up waiting on the first one. I'm just watching them fire off in firebug.
i used async:true in the setup just to see if that would help. But this should be the default.
I also placed timeout:5000 hoping that the first call would timeout and just keep running on the server while the other ajax calls would be free to continue. But all of them just timeout now waiting on the server.
Once I have the first ajax call running, all access to the domain is gone on my machine. I am stuck at that point with no solution except to restart the browser. Restarting the browser seems to kill the sessions on the server, but allow me to access pages on the domain again.
Where should I begin in trying to understand this issue? Anyone have articles that describe maybe doing a fire and forget call to the server?
While it is running, I call other php pages via ajax to do other things. All calls are being held up waiting on the first one. I'm just watching them fire off in firebug.
i used async:true in the setup just to see if that would help. But this should be the default.
I also placed timeout:5000 hoping that the first call would timeout and just keep running on the server while the other ajax calls would be free to continue. But all of them just timeout now waiting on the server.
Once I have the first ajax call running, all access to the domain is gone on my machine. I am stuck at that point with no solution except to restart the browser. Restarting the browser seems to kill the sessions on the server, but allow me to access pages on the domain again.
Where should I begin in trying to understand this issue? Anyone have articles that describe maybe doing a fire and forget call to the server?
Topic Participants
dan
Kevin Boudloche