Asynchronous JAVA Script & XML (AJAX)
An inclusive list of references is also offered on how traditional web application load unnecessary volume of information, but with utilizing AJAX download page design and fast upload of new data, which can reduce application's bandwidth by amount of data transfer. There is a strong necessity for a rich web application to be created at asynchronous interaction to help developers finish projects at well convenient time. AJAX technology is growing in supply chain and that's the main issue, but if issues can be mitigated it can be the top technology for developer in the near future.
AJAX is an application used for web development that enables web sites enhancement and appeal. In lesser terms, without Ajax, web pages would lack the level of appeal and usability inherent in the most popular websites (Lixandroiu, 2008). The main draw in the use of AJAX is to enhance an already accessible website. So the idea is to create a functioning website and then incorporate AJAX to enhance usability and functionality.
According to Lixandroiu (2008), "Another advantage of Ajax is a decrease in bandwidth use. Bandwidth in web hosting refers to the amount of data that can be communicated between user and server/website. In Ajax, bandwidth is used only to accomplish specific demands without requiring that the page be reloaded (which requires bandwidth, every dime a request is made). Contents are loaded on demand and HTML is produced locally from the browser. Ajax also allows programmers to separate methods and formatting of specific information delivery functions on the Web." (Lixandroiu, 2008)
Essentially, AJAX enables the use of cache to retrieve website information without using bandwidth to reload the website. Without the use of AJAX, there is a question with regard to the inherent efficiency, usability, and potential for loading error with the non-AJAX-based website. Therefore, rather than having to update and retrieve information from the website, AJAX enables cache to obtain the requisite information and refreshes the webpage accordingly.
AJAX is a functional application that has tremendous benefit for small and medium sized businesses that have capital constraints that perhaps prevent a greater share of bandwidth capacity to the website. As traffic to the site builds up, the inability for the site to load quickly and effectively becomes an issue. Additionally, programmers are able to incorporate a variety of languages into the development of specific goals as a conduit to further communication between the "client and server browsers." (Lixandroiu, 2008)
According to Jiaqi, Jie, Shujuan, (2009), "Traditional web applications allow users to fill out the form, and then send a request to the web server when the form is submitted. The server receives and processes the request, then returns a new page. This transaction wastes a log of bandwidth, as most HTML codes in the two pages are the same. Since each interaction of the application needs to send out the requests to the server, the response latency of the application depends on the server respondence period, which has resulted in the problem that the answering to the user interface is much slower than the local applications." (Jiaqi, Jie, Shujuan, 2009)
By adapting a multi-language format, the interface becomes extremely friendly to programmers that would like to adopt AJAX as their web application. According to Lixandroiu (2008), "Programmers can use whatever languages...
The industry trend appears to be the adoption of AJAX as the web application. The testing of AJAX states is achieved using invariants (Mesbah, Deursen, 2009). According to Mesbah & Deursen (2009), "With access to different dynamic DOM states we can check the user interface against different constraints. We propose to express those as invariants on the DOM tree, which we thus can check automatically in any state. We distinguish between invariants on the DOM-tree, between DOM-tree states, and application-specific invariants. Each invariant is based on a fault model, representing AJAX specific faults that are likely to occur and which can be captured through the given invariant." (Meshbah, Deursen, 2009)
According to Mesbah & Deursen (2009), "Malformed HTML code cam be the cause of many vulnerability and browser portability problems. Although browsers are designed to tolerate HTML malformedness to some extent, such errors have led to browser crashes and security vulnerabilities. All current HTML validators expect all the structure and content be present in the HTML source code." (Mesbah, Deursen, 2009)
Additionally, according to Mesbah & Deursen (2009), "To prevent faults, we must make sure that the application has a valid DOM on every possible execution path and modification step. We use the DOM tree obtained after each state change while crawling and transform it to the corresponding HTML instance. A W3C HTML validator serves as oracle to determine whether errors or warnings occur." (Mesbah, Deursen, 2009)
According to Matthijssen et al., "Ajax is popular: since the term was coined in 2005, a vast amount of Ajax enabled web sites have emerged, numerous Ajax frameworks have been created and "an overwhelming number of articles have appeared." A good example of an Ajax application is Gmail, which uses Ajax technologies to update only a part of the page when you open an email conversion, and to suggest email addresses of recent correspondents as you type." (Matthijssen, Zaidman, Storey, Bull, Deursen, 2010)
However, Matthijssen et al. also point to AJAX as a hindrance as it makes web development more complex. According to Mathijssen (2010), "Unfortunately, Ajax…
The protocols for such services are often difficult to distinguish from line noise. Even if such services were not trying to make their protocols difficult to reverse-engineer, Jabber's would likely still be easier to work with because of its XML basis. Software which supports XML can easily handle supporting new XML document tyes, such as the Jabber protocol, and a raw dump of the traffic would look familiar to
These are the researchers who completed the HTML, DHTML vs. AJAX application performance on XML (Yang, Liao, Fang, 2007) and the XML network optimization research completed across a replicated server and transaction-based methodology (Smullen, Smullen, 2009). Efforts will be made to collaborate with these researchers to learn from their expertise that has not been published in their analyses and also to collaborate on how to capture XML network optimization
When Web Services are created as part of a broader SOA initiative however, Chief Information officers (CIOs) and their staffs concentrate on setting a minimal level of performance for these specific aspects of AJAX performance. Conclusion There are also the issues of security (Chan, 2006) and the need for continually improving CSS performance and integration (Serrano, Aroztegi, 2007). The AJAX development language and its environments including Ruby on Rails (Bachle, Kirchberg,
To make sure there was as little variation introduced, Ruby on Rails was used as the programming language. Ruby on Rails supports TCP/IP and XML network integration through an Application Programmer Interface (API). The APIs to support TCP/IP and XML have been used for several years. As a result they are considered highly reliable and more accurate than other coding language APIs. Phase 3 With the test-bed created, the AJAX applet
82). Both desktop and Web widgets have the same basic components. Fundamentally, they use Web compatible formats, even if intended to run in a desktop environment. This means that the core of the widget is HTML and CSS code which contains the actual content of the widget, namely text, linked images/video or content pulled from a server of Web service. Alternatively, the widget content can be created using Flash, although