Web traffic reduction for infrequent update application using Green Ajax

Abstract

The classic web applications usually need a lot of bandwidth to provide the rich user interfaces. Since Ajax [8] was introduced, it has reduced the web server load and the data transfer to/from users' computers. By using Ajax, only a specific part in the web page can be requested to the web server [6]. However, it still cannot provide the real time data updating. The common approach to provide the real time data updating uses a timer to request a new data from the web server periodically [3, 4]. But, the requests sometimes do not get any new data. If the interval time to renew the data is too long, the data updating will come to the client late and some data received by the client may be lost.The proposed approach to solve the problem is creating an Ajax application which can receive a signal from the web server. The received signal will trigger the web application to renew the data from the web server. By limiting of requests to the web server only if a new data in the web server arises, as a consequence the traffic between the web server and the client can be reducible. The efficiency of web traffic will be measured by two matrices, the successful receptive percentage of the web application request to the web server and the bandwidth consumption of web application. In this research, an innovation of Green Ajax will be proposed. The idea of low bandwidth and low resource consumption are introduced. Mozilla Firefox and Firebug will be employed as the tools to measure the experimental results. From the experiments, the expected results of this research achieve 80% of the successful receptive percentage of the web application requests, no data loss percentage, and reduce 80% of bandwidth consumption.

Green Ajax Implementation on the WirelessLocal Area Network using Randomized Cue Applications

“…From the results, the number of times data that had been received by the client (Rcv), and the number of times requests that had been issued by the server (Req) were compared to get the Successful Receptive Percentage (SRP) [7]. Data Loss Percentage (DLP) were calculated by comparing the number of times data was not received timely by the client (Los) and the number of times update data was activated by the server (Upd).…”

“…Green Ajax sends fewer requests to the server compared to Classic Ajax. The less bandwidth consumption of Green Ajax reduces the network traffic [7].Furthermore, Green Ajax is still able to display the latest data using smaller amount of requests than Classic Ajax even though the server updates the data at the scheduled time and Classic Ajax uses the same interval time of data updating in the server for its TTR [8]. In addition, Green Ajax is also able to save the bandwidth when the frequency of updates is very frequent (High Frequency Update).…”

“…Green Ajax solves the problem by providing a new approach to send a cue from web server to the clients whenever an update arises. After the client receives a cue from web server, the client will issue the request to the web server [7]. Fig.…”

“…Green Ajax sends fewer requests to the server compared to Classic Ajax. The less bandwidth consumption of Green Ajax reduces the network traffic [7].…”

“…When the application receives the server's cue, the application will then send out a request [7]. The applications will display the latest Manuscript information without any involvement from the user.…”