. Topicala Page Index Token

A Journal about the experiences I have developing little applications in C#, Perl, Html and Javascript and talking about things new things that I use. Always Geeky; Always Nerdy; Always poor Grammer!

I am a Software Analyst Developer working in Southport, England but living in Liverpool. I develop mainly in C# and ASP.Net. I have been developing comercial software for several years now. I maintain this site (hosted at SwitchMedia UK) as a way of exploring new technologies (such as AJAX) and just generally talking about techie geek issues. This site is developed through a host of Perl scripts and a liberal use of Javascript. I enjoy experimenting with new technologies and anything that I make I host here.

Quick Search

Web www.kinlan.co.uk

Thursday, August 11, 2005

A Difference I think I have noticed between IE and Firefox concerning XmlHttpRequest

I am going to do a little bit more research on this but I think I have found an implementation difference between IE 6, IE 7 and Firefox, centering around XmlHttpRequest.

In both browsers, IE and Firefox, the developer can create a script that sends an HttpReqeust out via Javascript. The following code is pretty standard:

httpObj2.open("POST", url, false); // Asyn = true, Sync = false
httpObj2.onreadystatechange = parseSearchResponse;
httpObj2.setRequestHeader("Connection","close");
httpObj2.setRequestHeader("Content-Type","application/x-www-form-urlencoded");
httpObj2.send("query="+ escape(query));

The above code will send a request synchronosly (it will block at send). Now Internet Explorer will still call the function attached to the onreadystatechange event after the send has finished blocking. Firefox on the otherhand will not call it.

Which is the correct behaviour. If anyone knows email me at paul.kinlan@gmail.com

Technorati Tags
[feed], [feed], [feed], [feed], [feed], [feed], [feed]

Comments: [Add New]