AJAX Style processing icon

[shankwheat]

I'm experimenting with using a AJAX style "processing " icon. The
process I'm running in the background with xmlHttp is intensive and
takes a 5--10 secs to complete. Instead of my processing icon
appearing in the page, the page just freezes during the process until
it's finished. Is this the best way to display this kind of icon?
What can I do so this works right? Thanks

function stateChanged()
{
if (xmlHttp.readyS tate == 0)
{
document.getEle mentById("lblRe sults").innerHT ML = "<img
src='mozilla_bl u.gif' alt='loading..p lease wait'>"; //loading
}
else if(xmlHttp.read yState == 1)
{
document.getEle mentById("lblRe sults").innerHT ML = "<img
src='mozilla_bl u.gif' alt='loading..p lease wait'>"; //loaded
}
else if(xmlHttp.read yState == 2)
{
document.getEle mentById("lblRe sults").innerHT ML = "<img
src='mozilla_bl u.gif' alt='loading..p lease wait'>"; //interactive
}
else if(xmlHttp.read yState == 3)
{
document.getEle mentById("lblRe sults").innerHT ML = "<img
src='mozilla_bl u.gif' alt='loading..p lease wait'>";
}
else if (xmlHttp.readyS tate==4 || xmlHttp.readySt ate=="complete" )
{
document.getEle mentById("lblRe sults").innerHT ML = "";
<span id="lblResults " name="lblResult s"></span>

[VK]

On Apr 16, 7:12 am, "-Lost" <[e-mail] twrote:

JavaScripters should just rely on an existing library instead of learning the proper
way in which to do something?

AjaxRequest is well documented, so one is welcome to study what, how
and why is being made:
http://www.ajaxtoolbox.com/request/source.php

About the "learning curb":

Everything has its time and its place. Some people prefer the
practical learning, so they take a rather complicated task and hit the
wall until it's working - by obtaining the necessary knowledge on the
go from available sources. If OP decided to learn JavaScript over
making a well working ajaxoid then it's fully OK. If OP needs a
working interface right now for a live project then the "learning
curb" may take several months with all oops reported by frustrated
customers and not by an in-house QA. That can become a way too
expensive learning experience.

1) run-time error on reading XHR property after network errors
(despite status=400)
2) send null or "" for GET sensibility for some UA versions
3) GET request length limit on different IE versions
4) multiple async requests caveats which would be a separate nested
list right here

How much time does it take to simply _arrive_ to these questions out
of foggy error reports from your customers?

In this respect AjaxRequest is not really a "library" like say
prototype.js
It is merely a sophisticated interface over all kind of bugs, under-
implementations and limitations of different IXMLHTTPRequest/
XmlHttpRequest implementations .