• 1
• 2
• 3
• 4
• 5

ajax andrew archive article asyncrequest bad bit block blog call callback called calmpear catch catche check code comment comments definition delicious development diaz dustin elegantly entry fast faster file filed function functiono getxhr graham handlereadystate handlereadystatehttp hit http httpopenmethod internet javascript js lazy leave len links logic machine making memory msxml msxmlxmlhttp newer object october optimization optimized oreadystate original ostatus page params pattern performance piece pm poll post postdata posted problem read reason request requests response return returned run september speedy st tags technique techniques test time trackback true updated uri url var version web webdev work working xhr xmlhttp xmlhttprequest

Keyword Cloud Navigation Map

Sometime ago I was messing around with various techniques for ways that we can optimize asynchronous calls to the server via XMLHttpRequest (and the ActiveX equivalent of XMLHTTP). I wrote about one of those techniques known as branching in an article for Digital Web Magazine called Seven JavaScript Techniques You Should Be Using Today back in April, however, there was a flaw in the function that when one request is made before another one is finished, you would run into an error since it is using the same reference to the instance object for the request. That’s cool in theory, but bad in practice. The benefit you get with that is that you never create more than one XMLHttpRequest object for all your requests. This is fine for light weight use, and when you know for sure that you won’t be making frequent requests simultaneously. But when does that ever happen? Really.

Read Full Tutorial...