|var ajaxManager = $find("<%= ram.ClientID %>");|
6 Answers, 1 is accepted
The question set forth has been addressed in the support ticket that you opened on the matter. To avoid duplicate posts, we can continue our communication there.
the Telerik team
Please let me know if you find any solution to solve this issue?
I'm still having problem with reliably calling ajaxRequest() during page unload. Sometimes the call could get through and the other time it couldn’t (especailly with IE6 SP3). Is there a way that I can make a synchronous ajax call? Therefore, I can make sure the call is completed before the page gets unload.
Here is my code, I tried to call SaveOnExit() inside PageUnload(), Unload() and BeforeUnload(). But none of them are as reliably as I'd like. I event added some delay, but it still doesn't help much. It seems to me if I could make a synchronous ajax call so the page won't get unloaded until the response is coming back is the only way.
var ajaxManager = $find("<%= ram.ClientID %>");
Another option in this case would be to use a RadWindow, and use the onclose client side handler, to handle this setup.
All the best,
the Telerik team
IE7 has 2 maximum live connections, when an ajax calls is interrupted, IE does not know how to close the connection, this results in a hang after 2 ajax calls within unload event. It is a serious issue that Firefox doesn't have. User has to either wait until the connection times out or force IE to close.
The only reliable solution is synchronous call within unload event.
Summary of the issue from MS support:
"It looks like IE will not send new requests to the same domain when the hang happens. What I can guess so far is, IE somehow doesn't know the connection should be closed if a user manually interrupts the AJAX request by closing the tab. By default, as you may know, IE only allows two subsequent connections to one domain. I've contacted our development team for a confirmation about this issue. They may need some time to come to a final conclusion. I'll follow up and update here. "
Here are links that discusses the issue:
http://bytes.com/forum/thread643080.html (contains a demo page that demonstrate the issue)
http://www.eggheadcafe.com/software/aspnet/33118270/ajax-and-ie-crash.aspx (Microsoft support replying to a user with the issue)
I hope this helps.