It's because of memory leaks. We need to help the browser to get all the acquired memory free afterwards. There are some issues that objects and especially DOM-nodes connected with each-other especially in case of circular references couldn't automatically resolved by the browser.
That's the idea behind disposing. But the disposer is not a memory management tool. We don't directly can control the browser and tell him to free memory now. This is the reason why pooling of objects etc. is interesting sometimes. Hope this helps. Cheers, Sebastian dperez schrieb: > Hi, > > Just for curiosity, why all objects are disposed in the window.unload event? > For freeing memory? Isn't the memory automatically freed by the browser? > Or perhaps for giving the objects a chance for doing something special? > If this is the case, woudn't this slow down the broswer a little > unnecessarily? > Thanks in advance for any light in this area. > > Regards, > David ------------------------------------------------------------------------- Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 _______________________________________________ qooxdoo-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
