AJAX-Tips
HTML based websites interact with their users based on commands. Without any input from the user, no response is made. The connection is paused until further command is received from the user. This is very feasible for HTML websites since it does not need to have complicated code. This type of website could load fast even with a dial up connection. This type of websites could even perform faster when they are loaded with DSL connection.
In this setting, Request/Response in HTML is fast and interaction is based on what the user needs. However, it does not maximize bandwidth connection. The interface is very simple but there certainly more than simple Request/Response setting.
There are web languages that have pushed the boundaries of internet connection. Flash and Java requires strong internet connection before the online application could be loaded and used. Java’s robust functionality provides secured and interactive interface while Flash became a popular media application especially for streaming video.
While the have pushed the boundaries for bandwidth connection, the variation of Flash and Java especially in building applications is very slow. The key factor for this delay in development is the requirement Flash and Java downloads before it could be used as an application. Although almost every computer in the world has installed Flash and Java in their application, the computer has to be updated constantly to run the latest Flash and Java based application.
Ajax on the other hand does not require anything from the user except to have a strong internet connection. Since it is based on JavaScript, the client side functions will be loaded directly from the server. No need for downloads before any Ajax based application could run on a computer.
What made Ajax more impressive is its ability to “anticipate” the user’s need within the application. Using multi-phased downloads; the developer could prepare the website for the user.
The process is fairly simple, the developer starts with a simple homepage with simple information needed by the user. If the user stays on the same webpage, the functions of the application will be prepared to anticipate any commands from the user. If the user leaves after landing on the webpage, the application still saves on bandwidth because it did not load additional functions.
Although this seemed to be a fair setting for Ajax, it has its downside. The functions should be as simple as possible in order to require lesser bandwidth. As the user stays on the homepage, much of the bandwidth will be spent on the homepage and only a small amount of connection is left for the functions. This will help not only to effectively load the application but also to accommodate web crawlers for search functions.
Multi-phase downloads in Ajax is one of the key features of this development language. Although it could be very challenging for most developers, the benefits of the application will always be there and will eventually outpace simpler HTML based websites.
