Hi Pops,
Be sure to keep John in the loop on your efforts. He's a very
open-minded guy.
Rey
Pops wrote:
On Aug 28, 6:17 pm, digitarald <[EMAIL PROTECTED]> wrote:
The easiest fix, instead of using a
periodical checker which seems kind of weird on the first blush, is to
avoid closures during coding ...
Just for clarfication.
The idea of polling for non-atomic states is a Sync 101 violation.
There are numerous classic examples in the books to illustrate it and
if you don't this long enough, it tends you bite you eventually
The idea of serializing an asychronous capable protocol is not.
This is par for the course - iff you create your own I/O thread
handlers.
So the "wierd" thing is the justifcation - to cure a bug (related to
JS/User Agent clean up issues).
It would not be a "wierd" thing is they simply said
"Due to the varying behavior of the XHR protocol, from OS to OS,
from
browser to browser, we are Single Sourcing a consistent API
design behavior for jQuery $.ajax() method."
which is a 100% PERFECTLY SOUND JUSTIFICATION.
The problem is that the 13ms doesn't SINGLE SOURCE it anymore. :-)
Change the 13ms to 1ms and now you single source it. I believe John
acknowledge that much.
But I still think it is wrong to remove the XHR callback behavior. As
an option, that needs to be added back into jQuery.
Anyway, I have working on my own plugin for $.ajax() and I proved you
can do it both ways without the leaks. But I really hate changing 3rd
APIs - it defeats the purpose. :-)
I can perfectly see John's delima here because he lumped and tied in
so many other ideas, that making a change will most like cause
something to be broken.
So far I have not seen it. but I want to do more testing with some of
the other ajaxSettings.
--
HLS
