Couldn't you just use beforeSend to intercept the XMLHttpRequest object and add your own callback handlers to it directly? You'll have to put up with all of the aforementioned memory leak issues, but you'd get access to all of the state changes that you're looking for...
--Erik On 8/25/07, Pops <[EMAIL PROTECTED]> wrote: > > Dan, > > Thats exactly how I do look at code - always. I am a commercial > developer. Products are used across the board. It is was one reason > we avoided using javascript for many years (or atleast not these more > advanced levels). > > In this case, I don't think setting a timer and bypassing the > implemented xmlhttpRequest() state machine protocol would work > consistently. To illustrate my point, you already get different > behavior on what states are skipped and changing the frequency will > give you different behavior. > > On the other hand, each protocol is designed to behave to provide each > state and it must be signaled - otherwise it is really broken and > something the vendor must address pronto. That should not be jQuery's > responsibility. > > In my products development experience, when you begin to "kludge" in > solutions to get around a specific vendor problem, while that may work > in the interim, that generally invites inconsistencies. jQuery is > not cross browser ready in my opinion. Far too many items are not > being tested well enough with IE. > > Of course, whats fundamentally different is the open source > mentality. The idea of using open source is relatively new for me. > All the old reasons for not using it, are the same if you catch my > drift. Yet, that is the way it is today. Can't no longer ignore it. > So it takes a different mindset to get use to it - the idea of > accepting lower quality software "as is" (and I am not saying jQuery > is low quality) than what it normally would expected to be in a > commercial environment. Of course, being that is open source, give > the community the power to analyze the code - and I can't help myself, > its in my nature to look at these things. > > You know whats difference? > > Unlike the past with free software, no longer are you seeing the > proverbial - "Its free, stop complaining." <g> > > So thas good atleast - the "professionalism" is growing in the open > source world. > > -- > HLS > > > > On Aug 24, 10:17 pm, "Dan G. Switzer, II" <[EMAIL PROTECTED]> > wrote: > > Pops, > > > > >Ok, there is always a reasons for something. I appreiciate you taking > > >the timeout to share it. > > > > One thing to keep in mind is that jQuery is intended to be a cross-browser > > library. Just because the XHR object works one in one browser, does not mean > > it works correctly in all the browsers on all platforms. > > > > The goal is to provide a consistent behavior across all browsers and > > platforms whenever possible. > > > > Just keep that in mind when looking at code... > > > > -Dan > >
