Ajax Framework Comparison Tools article

| by Rob Thornton Follow 0 Followers on Dec 15, 2006. Estimated reading time: 1 minute |

A note to our readers: You asked so we have developed a set of features that allow you to reduce the noise: you can get email and web notifications for topics you are interested in. Learn more about our new features.

A new article on BEA's Dev2Dev site provides a way to sort through the numerous Ajax frameworks that are available today. The goal of the technique is to make it easier to understand the distinctions between the various frameworks by placing them on a set of axes including declarative versus procedural and client-centric versus server-centric.

Gary Horen, the Program Manager for Ajax and Languages at BEA, wrote the article because there are so many Ajax toolkits available that it can be hard to winnow down the choices and find the correct one for a project. He describes his goal as:

This article attempts to sort through these frameworks and map some of the characteristics by which they can be compared. The hope is that the reader will come away with some tools to use for breaking down the collection of Ajax offerings in ways that make it easier to understand distinctions between them, narrowing down the subset that needs to be looked at, and making better-informed choices.

Horen breaks down the frameworks along four axes:

  • Open source vs. commercial
  • Comprehensive framework vs. individual components
  • Declarative vs. procedural
  • Client-centric vs. server-centric

He describes each of the axes, the pros and cons of each end, and what to consider when making a decision on it. For instance, for the comprehensive framework vs. individual components axes, he describes the issues to consider as:

Making a choice along this axis is often related to the age of an application: A new one generally has an easier time dealing with the assumptions made a by a comprehensive package. To make incremental improvements to an existing Web application, it can often, although not always, be easier to integrate code scraps or objects. Scraps and individual components can require more programming, because they operate at a lower level. Comprehensive frameworks make assumptions that make them harder to integrate with each other, and are harder to use in a portal (because sometimes their assumptions conflict with ones made by the portal container).

He then goes through five frameworks: Prototype, DWR, Dojo, Backbase, and GWT and describes where they fall on the axes. His final section is on tooling, where he mentions client-tools from the Mozilla Foundation and the Eclipse Ajax Tooling Framework as well as the server-side tools BEA Workshop Studio and GWT Designer.

Rate this Article

Adoption Stage

Hello stranger!

You need to Register an InfoQ account or or login to post comments. But there's so much more behind being registered.

Get the most out of the InfoQ experience.

Tell us what you think

Allowed html: a,b,br,blockquote,i,li,pre,u,ul,p

Email me replies to any of my messages in this thread

Check out also Visual WebGui which provides an alternative for GWT on .NET by Guy Peled

Here is a short screncast demonstrating developing with Visaul WebGui.


Allowed html: a,b,br,blockquote,i,li,pre,u,ul,p

Email me replies to any of my messages in this thread

Allowed html: a,b,br,blockquote,i,li,pre,u,ul,p

Email me replies to any of my messages in this thread

1 Discuss

Login to InfoQ to interact with what matters most to you.

Recover your password...


Follow your favorite topics and editors

Quick overview of most important highlights in the industry and on the site.


More signal, less noise

Build your own feed by choosing topics you want to read about and editors you want to hear from.


Stay up-to-date

Set up your notifications and don't miss out on content that matters to you