Web Info & Tutorials

je suis une jeune maman,qui elegant vetements de fillette 18 mois et + a donner.je me deplace et cela m aiderais enormement.un gros merci….vous pouvez me telephoner au 514-606-0994 ou au 514-597-0

Sebastian of the qooxdoo team is happy to see Dramatically improved IE7 JavaScript performance, with some of the quooxdoo demos run as fast as Firefox 1.5.

What is interesting is the fact that the object creation leakage talked about often seems to be fixed.

If you have many objects created, which are simply accessible in the current scope, all methods and features of JavaScript slow down dramatically. Yeah, right, the entire execution speed drops significantly. No other browser besides IE shows such a strange behavior. It is quite interesting that IE6 really gets slower the larger the total number of (accessible) objects. Sure, it is logical that more instanciated objects need more memory, but it is not logical that at the same time this will dramatically reduce the performance of any code (that is not even accessing this data).

With the release candidate RC1 of their new browser version IE7, it seems that they have finally fixed this issue. You can test it yourself in this test case, which has been available in qooxdoo for several months to analyze and measure the IE performance problems. Please look at status bar of your browser (maybe you need to enable the status bar in the IE7 security settings). It will display the execution time of each loop while a large number of objects exists. On my machine the IE6 needs ~1400ms, while IE7 needs ~30ms, which is roughly the time Firefox 1.5 needs. Definitely incredible! Bright future for modern web applications.

Sebastian Werner has posted some good news over on the QooXdoo blog today - that the Javascript performance of the upcoming Internet Explorer 7 has been greatly increased.

Really good news. My vocabulary may to be too limited to tell you how great the latest changes in IE7 RC1 are. Microsoft announced that they have “recently made some great fixes to our engine to improve the garbage collection routine and to reduce unbounded memory growth.” and that one “should see noticeable improvements on AJAX sites in the Release Candidate we shipped last week”. Yes indeed, we do see tremendeous improvements.

He gives the example of the qooxdoo framework running “much faster” in the new update (at times, even faster than Firefox 1.5). You can check out the demos and compare them if you’d like to see the result.

The reason behind this dramatic improvement? Microsoft decided to fix something that’s been causing problems in Javascript for years now - the more objects in the same scope you have, the slower things get. He also includes a test case to help illustrate this point specifically.

David Arthur, like many, has had problems with the caching issue that Internet Explorer seems to have with Ajax connections:

If you’ve been working with the Ajax framework long enough, i’m sure you’ve run into at least a few speed bumps thanks to Internet Explorer. Not a day goes by that i don’t have to rewrite a line of code, or tweak my css in order for IE to render what i think it should. But alas, this is the nature of software that comes from a company that views Standard Compliances as recommendations.

He describes his problem - grabbing a new image with an Aajx request, a seemingly simple task - and the results of his queries. IE decided caching it was the “in” thing and wasn’t going to grab anything new. He tried all sorts of hacks and fixes to try to get things working, but to no avail. Finally, after finding this entry on Wikipedia, he stumbled across a solution - using POST over GET.

While he was figuring it out, though, there were also lots of comments being made to the original post with hacks to get around the issue - so many that he wanted to create a new place for them all to be shared. In this post he includes two of the suggestions, including using something like a timestamp to change up the URL and adding in an unused POST variable.