Damn I thought I had it but now I am confused again (doesnt take much).
Correct me if I am wrong but looking at Jakes code the processReqChange function gets called 4 times 1 for each of the readyState - once it reaches 4 it continues. So the code is not in a continous loop but rather waiting for a state change.
Are you saying Bob that when you did your view navigator the event handler never called drawViewNav() ? Because if it did you wouldnt need the timeout right ? As for handling a timeout wont that return a different HTTP status code which means you can handle it (aka non javascript version of the navigator).
Bob,
Damn I thought I had it but now I am confused again (doesnt take much).
Correct me if I am wrong but looking at Jakes code the processReqChange function gets called 4 times 1 for each of the readyState - once it reaches 4 it continues. So the code is not in a continous loop but rather waiting for a state change.
Are you saying Bob that when you did your view navigator the event handler never called drawViewNav() ? Because if it did you wouldnt need the timeout right ? As for handling a timeout wont that return a different HTTP status code which means you can handle it (aka non javascript version of the navigator).
Mark