AJAX - Executive Summary
March 03, 2006
The biggest problem that we face in web applications is the time taken for reloading Web Pages. This depending on what you have put on the page and the speed of your connection, can range from average to slow. In the meanwhile, think of an application where the page is refreshed in an instant. Or if the page has to come from the server, it does so in the background. So no more hour glasses, so to say, you see. A big headache goes away.
Now, imagine having the ability to use the following browsers viz. IE, Firefox, Safari and Opera (7.0 and above) without worrying about the quirks of each one of them. Think of the page getting refreshed intelligently depending on the type of your internet connection (dial-up , broad band etc.) Move away from page based design to event controlled interface. Intelligent User interface, which minimizes the number of clicks, for a rich user experience. And all this, without having to procure a plug-in or an applet and based on Open Standards.
Sounds like a dream. Please welcome AJAX! Again.
A small detour : As per Greek Mythology, Ajax was the son of Telamon, the king of Salamis. He was a mighty hero of the Trojan War.
There are quite some number of AJAX IDE's like BackBase, JackBe and some others. Some of the tools have a visual workflow. Google uses AJAX in GoogleSuggest and GoogleMaps. Others have also started to get a feel of this powerful paradigm.
By 2010, it is expected that 60% of all applications on the web would be RIA's. Ajax will definitely be one of them, if not the leader. The others like XUL and XAML (part of Avalon - Microsoft) are also contenders.
Time to sing 'In the junmighty jungle, the Lion sleeps tonight'.
Rajesh Menon (Nickname Guru30)
e-mail: [email protected]