BOSTON -- A year or so ago, most developers looking to work with Ajax had first to create their own framework for Ajax. It was either that or just throw a bunch of UI components together -- not a great idea. Clearly, Ajax has a server-side element, but action on the client-side has gotten the bulk of attention.
By submitting your personal information, you agree that TechTarget and its partners may contact you regarding relevant content, products and special offers.
These days, a variety of component sets are available as open-source and commercial frameworks. Among the Ajax frameworks considered at this week's Ajax Experience Conference in Boston were Prototype, Dojo and script.aculo.us. Microsoft has responded to the call for Ajax as well, with a framework called ASP.NET 2.0 AJAX Extensions, known in its gestation period as Atlas.
"We look at [ASP.NET 2.0 AJAX Extensions] as being a framework on the client. So there is a component architecture there," said Brad Abrams, group program manager, .NET Framework, Microsoft. Client-centric Ajax applications can exploit DHTML, use Ajax for data, services and composition, and enable new interactive experiences, he indicated.
Abrams pointed to the beneficial features of ASP.NET 2.0 AJAX on the serverside, noting that this framework works with existing server application models, allowing developers to keep present UI and application logic on the server.
"Its easier for an ASP.NET developer to use the server-side controls," he said. In a tool demo, he showed use of an Update Panel to compose database connections using familiar drag-and-drop techniques for use by Ajax clients.
ASP.NET 2.0 AJAX supports both client- and server-centric approaches, he said. The software is available for download, and just went to beta last week.