1.4.0 is quite old by this point. I don't know if 1.5.0 would fix your problem but you might want to cook up a test to see. Either way it is probably worth it to update your code every once in a while just to eliminate a few variables when bringing up questions like this.
If you can eliminate (or reduce) ajax requests on load your page will be much faster and much less problematic. I have no idea how your server-side code works but would it be possible to generate a script tag at the end of the page that calls your onCompletes or whatever directly without initiating an Ajax request? I did some shallow research and it appears there is an abort method for xmlhttprequest, and Prototype never calls it under any circumstance.. Maybe Prototype should cache all active requests and on unload it should call abort on any active requests? It sounds like that may be a possible fix to your problem. Cook up a simple test and see if it does. If this fixes your problem I think it is definitely worthy of a ptach, but good luck getting it accepted if you write it yourself and pass it off as your own idea ;) You could probably implement a wrapper yourself easily enough as an alternative... If calling abort does fix the problem, bring this up in the Prototype Core group for further discussion of a patch. If you write a patch, consider writing it for the new ajax branch recently opened: http://groups.google.com/group/prototype-core/browse_frm/thread/43c13d4b233b20fb Colin szaroubi wrote: > Hello, > I am new to the list. I am currently using prototype.js version > 1.4.0, for an application we are developing to be used with IE6&7. > I am having a problem which can be triggered as so: > > 1) Open Window with 10 Ajax Request connections starting on Load > 2) Right after the page loads (and you feel like the Ajax Requests > have been triggered) close the window > 3) Repeat steps 1 & 2 about 3~4 times > 4) All other Ajax Requests within IE session will not work (I used > a network scanner to sniff the packets on my network and see that the > Ajax Requests are not even sending a request) > > > The problem happens with both IE6 and IE7. Upgrading to 1.5.0 is > not really an option as we have found other problem in 1.5.0 which > break under IE7. > The problem seams to be a "connection leak" or "dangling > connection" problem in IE (connections are not being closed correctly > and IE thinks that they are still open). > > Has anyone seen a problem like that? Does anyone have an idea where > I can look? Possible work around (Setting a reg key to increase the > number of allowed connections in IE (even if it's just a not very > robust workaround)) ? > > Any help would be appreciated. > Thank you for your time > > > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Spinoffs" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/rubyonrails-spinoffs?hl=en -~----------~----~----~----~------~----~------~--~---
