Internet Explorer will be stuck when too many connections have been set up in the page at the same time. Let's build a fake XHR object to solve the bug for Internet Explorer browser.

As one of the key features in ASP.NET AJAX, calling a script method from a client would be used a lot when buliding AJAX applications using ASP.NET. There's a server side caching mechanism, but how can we cache the responses on the client side to get a better performance?