Zach, Your modification is the closest I have come to getting this to behave somewhat normally, particularly for finding the readyStates. The result, in IE6, with your modification, is...
The current state is 1 The current state is 1 The current state is 2 The current state is 3 The current state is 4 A little weird, but I am able to find all the different "states" of the request. However, the problem remains, what if the status changes during this process? Now, some of you might be wondering, why is it important to know this? Just check for status 200 and state 4 and be done with it, eh? Well....that is fine if you are working with a website for John Doe's Delicious Deli (or any other non-private entity). But, this may be needed for some types of private transactions and certain data that must be protected by law or other reasons. In certain situations, what is happening at the socket level is required knowledge and must be monitored precisely and in its entirety. The entire "transmission" needs to be successful or, if a failure occurs during the process (not just the end result), certain steps must be taken to ensure that the data is still protected. I understand you could encrypt this data or perhaps use a different protocol, but in certain industries you will need to be able to monitor everything in the most minute (and seemingly mundane) detail. If anyone can determine a workaround to get the exact status of each state, it would be interesting to know. Regards, ~K On Mon, May 25, 2009 at 5:19 AM, Zach Anderson <[email protected]>wrote: > document.getElementById("updateArea").innerHTML = currMsg + "<p>The > current state is " + xhr.readyState + "</p>"; -- If you understand, things are just as they are. If you do not understand, things are just as they are. --~--~---------~--~----~------------~-------~--~----~ Our Web site: http://www.RefreshAustin.org/ You received this message because you are subscribed to the Google Groups "Refresh Austin" group. [ Posting ] To post to this group, send email to [email protected] Job-related postings should follow http://tr.im/refreshaustinjobspolicy We do not accept job posts from recruiters. [ Unsubscribe ] To unsubscribe from this group, send email to [email protected] [ More Info ] For more options, visit this group at http://groups.google.com/group/Refresh-Austin -~----------~----~----~----~------~----~------~--~---
