• 1
• 2
• 3
• 4
• 5

actual ajax amount app application applications approach based beating benchmarking bit brad browser build building calls cases choosed client code comments consumed corporate create creating data dave dead december developers display dom easier easily engine eval fast faster ff figure filtering find firefox format function good google great hand high highly html http huge human including january javascript johnson js json languages latency load making mash method object objects output page parameters parts people performance pm post previous process processing property public readable records response responsetext responsexml results rss ryan saving script serialize server service show shows side slow slower snippit snippits sorting st state string tag takes test tests text time title tree typed useable user users var web work xml xmlhttprequest xslt

Keyword Cloud Navigation Map

There has been a great discusson over at Quirksmode [1] about the best response format for your data and how to get it into your web application / page. I wish that I had the time to respond to each of the comments individually! It seems that PPK missed out on the option of using XSLT to transform your XML data to an HTML snippit. In the ensuing discussion there were only a few people mentioning XSLT and many of them just to say that it is moot! I have gone over the benefits of XSLT before but I don't mind going through it once more :) Just so everyone knows, I am looking at the problem _primarily_ from the large client side dataset perspective but will highlight areas where JSON or HTML snippits are also useful. Furthermore, I will show recent results from JSON vs XSLT vs XML DOM in Firefox 1.5 on Windows 2000 and provide the benchmarking code so that everyone can try it themselves (this should be up shortly - just trying to make it readable).

As usual we need to take the "choose the right tool for the job" stance and try to be objective. There are many dimensions that tools may be evaluated on. To determine these dimensions let's try and think about what our goals are. At the end of the day I want to see scaleable, useable, re-useable and high performance applications developed in as little time and for as little money as possible.

Read Full Tutorial...