InfoQ

InfoQ

News

My Bookmarks

Login or Register to enable bookmarks for unlimited time.

The content has been bookmarked!

There was an error bookmarking this content! Please retry.

Picking an Ajax Framework

Posted by Scott Delap on May 03, 2007

Sections
Development
Topics
Java ,
Web Frameworks
Tags
Prototype ,
DWR ,
GWT ,
Scriptaculous ,
Dojo ,
AJAX
Dr. Dobbs is currently featuring a case study of the Ajax framework selection process of a development team at T. Rowe Price. The team evaluated a number of popular Ajax frameworks for use in their next generation application:
  • Dojo 0.3.1 (dojotoolkit.org).
  • Prototype and Scriptaculous 1.4 (www.prototypejs.org and script.aculo.us).
  • Direct Web Reporting 1.0 (getahead.org/dwr).
  • Yahoo! User Interface Library 0.11.1 (developer.yahoo.com/yui).
  • Google Web Toolkit 1.0 (code.google.com/webtoolkit).
After initial review GWT was eliminated due to the legacy team division of UI and back end developer along with the requirement of learning a new Java based API. DWR was also eliminated due to the patch needed for the version evaluated to work with the Websphere Application Server used by T. Rowe Price. This left Prototype, Dojo, and Yahoo UI for continued evaluation.

The case study then goes on to compare how each framework fulfilled the requirements of creating a tabbed ajax widget and a dynamic "hub" widget with a title bar. All three required custom work for the desired tab widget functionality with Dojo providing the closest functionality out of the box. The team then moved on to look at load times:

...The smaller the footprint of the framework used, the less likely performance degradation occurs. The total compressed JavaScript file sizes required by YUI (22K) and Prototype (32K) are significantly smaller than the single custom Dojo JavaScript file, which is about 200K. All three libraries performed well with a high-speed connection; however, the YUI and Prototype/Scriptaculous prototypes performed faster with 56K dial-up connections...

Finally the team looked at overall ease of development. The consensus was that Dojo provided more features and widgets but customization was harder due to the number of files needing modifications. Yahoo UI was ultimately choose due to its well documented code and detailed tutorials on the Yahoo website.

Good comparison... by Mittal Bhiogade Posted
extjs by Dominik Dary Posted
Re: extjs by ZedroS Schwartz Posted
JQuery by Janos Haber Posted
Re: JQuery by waqas zahoor Posted
  1. Back to top

    Good comparison...

    by Mittal Bhiogade

    I liked the process how the comparison between different ajax frameworks was done using pugh matrix.. I hope that's what is called.

    But in my opinion, DWR is best ajax framework if there are no requirements to have fancy widgets may be just tables on view pages that refreshes asynchronously

  2. Back to top

    extjs

    by Dominik Dary

    why not use a layer above theese frameworks: extjs.com/?!

  3. Back to top

    Re: extjs

    by ZedroS Schwartz

    Thanks to Java popularity, I guess we all could speak about another framework, so... Whatever, it's still interesting to read to know more about the numerous existing frameworks.

  4. Back to top

    JQuery

    by Janos Haber

    Ok, but where the jquery?

  5. Back to top

    Re: JQuery

    by waqas zahoor

    i think JQuery is one of the best in business

Educational Content

Attila Szegedi on JVM and GC Performance Tuning at Twitter

Attila Szegedi talks about performance tuning Java and Scala programs at Twitter: how to approach GC problems, the importance of asynchronous I/O, when to use MySQL/Cassandra/Redis, and much more.

10 tips on how to prevent business value risk

One category of risk that project teams need to ensure they address is business value failure – delivering a product that fails to provide value for the business investor.

Interview: Software Systems Architecture: Working With Stakeholders Using Viewpoints and Perspectives

InfoQ spoke to the authors of Software Systems Architecture on a couple of new topics, the System Context viewpoint and Agile, which have been added to the second edition.

Beauty Is in the Eye of the Beholder

Alex Papadimoulis discusses ugly code, where it comes from, how to avoid it, and how to get rid of it.

Architecting Visa for Massive Scale and Continuous Innovation

John Davies examines Visa’s architecture and shows how enterprises have architected complex integrations incorporating Hadoop, memcached, Ruby on Rails, and others to deliver innovative solutions.

Max Protect: Scalability and Caching at ESPN.com

Sean Comerford unveils ESPN.com’s architecture, what components are used and why, and the current changes the website goes through.

The Seven Deadly Sins of Enterprise Agile Adoption

Are there repeated patterns of failure on Enterprise Agile Enablement efforts? Sanjiv and Arlen discuss Seven Deadly Sins to avoid when adopting Agile in an enterprise.

Questions for an Enterprise Architect

Erik Dörnenburg answers: What is Enterprise and Evolutionary Architecture?, discussing 4 issues: Turning strategy into execution, Ensuring conformance, Where do the architects sit? Buying or building?