- Silicon Valley's 19 Coolest Places to Work
- Is Windows 8 Development Worth the Trouble?
- 8 Books Every IT Leader Should Read This Year
- 10 Hot Hadoop Startups to Watch
Page 2 of 2
But it's not always easy to add AJAX elements to an existing Web application. It depends how entwined the application logic and presentation layer are. If they are distinct, a developer may have to modify only a small percentage of the application code base.
"We've seen instances where they are separate enough that it's extremely easy to do. Even a client/server application could have been developed under an n-tier infrastructure," says Luis Derechin, CEO and cofounder of JackBe, which makes AJAX toolkits and infrastructure platforms. "Other times, it's so embedded that it's a mess."
Another factor driving corporate interest in AJAX is the chance to move client/server applications to the Web. Companies can mimic the features and look and feel of a client/server application while gaining the management and administration benefits of a Web application, says Ted Farrell, chief architect for application development tools at Oracle.
"People have started missing their old desktop clients, where things really were interactive and dynamic," Farrell says. "So more push has been made to keep the single distribution model of the Web, so companies don't have to go through the hassle of distributing software to everyone's desktop, but still get the rich interaction associated with a desktop client."
Another key feature attributed to AJAX applications is their ability to reduce the network load compared with traditional Web applications.
In theory there should be fewer round trips to the server and more client-side processing of the information if programming is done well, says David Boloker, CTO of emerging technologies at IBM. "If you're sending down XML and then the client works on the XML, as long as you're not continuously sending little bits of XML up and down, the server is going to have a lot more cycles free," he says.
Gartner's Skorupa agrees. "Well-coded, well-structured AJAX applications can improve responsiveness, because you can do incremental updates to the screen, rather than pulling everything down, which can reduce the number of round trips," he says.
However, some of the things Web developers are doing with AJAX to make applications more responsive can have a negative effect on network performance, Skorupa says. For example, if there are 10 embedded links on a particular screen, developers use AJAX technologies to open all 10 links and download the information even before a user requests it. "Just in case you might want it, it will be there," he says. "That could put a whole bunch of extra load on the network."
Such pitfalls are dangerous. People have a tendency to think AJAX is easy, because it encompasses familiar technologies. But consider the resources Google employed to prototype, test, tweak and deploy its AJAX applications, Skorupa says. Google has the means to hire some of the very best programmers in the business, but most enterprises don't.
"You've got to assume a lot of enterprise code is not going to be that well written; it's going to be added piecemeal to current applications, and it's going to be written by people who've never done it before and who don't understand the programming model," he says.
Right now, a lot of companies are experimenting with AJAX in small doses, which is a good way to start. But until companies think strategically about how the proper use of these technologies can facilitate a clear business objective, they shouldn't expect miracles by adding an AJAX widget to a Web site. "You can't take an old Pinto, slap on a new coat of paint and expect it to outperform a Ferrari," Derechin says.
|Hype vs. reality
Read more about software in Network World's Software section.