Ajax is an acronym for Asynchronous JavaScript and XML, and at its heart is the XMLHTTPRequest object, which is part of the XML DOM (Document Object Model).
The XML (Extensible Markup Language) Document Object Model defines a standard way for accessing and manipulating XML documents. The DOM enables JavaScript to completely access XML or XHTML documents by providing access to the elements which define the structure. The accessibility is possible through a set of intrinsic JavaScript objects that focus on DOM manipulation.It is required to parse the responses that we receive from the server side when we create an XMLHTTPRequest (XHR). As mentioned earlier, the XHR is the core of the Ajax model and without it the model would not exist. This is the piece of the Ajax puzzle that has created the recent buzz because it allows HTTP requests to be made to the server without refreshing the browser.
Ajax is a powerful collection of languages that, when brought together, create extremely intuitive user interfaces and client-side interactions. Although this is true, there are many developers who get so excited by the hype surrounding it that they simply throw the code into their applications without measuring the benefits of using it beforehand. Not every web application has a need for Ajax, but there are many parts of an application that can be enhanced by utilizing its benefits. You will learn usability patterns that will handle feedback, server-side form validation before we even submit the form, and Ajax-enabled components that can enhance sections of our web applications without overdoing it. Ajax is also great to use if you would like to make a server-side connection and possibly a database interaction without refreshing the browser. This is what makes Ajax so powerful because it allows us to interact with the server, receive HTTP status codes, save data to a database, and determine what to present to the user without ever refreshing the page. This request/response pattern can continually persist as a desktop application does, but Ajax-enabled web applications are, well, on the Webaccessible by anyone with a connection, without any downloads or shipping costs for delivering large fancy boxes. The Web is the new desktop, and we are on the verge of a major software shift that we can actively participate in as the pioneers of on-demand information.
Ajax can be a valuable connection between the interface and back-end logic, allowing the back end to be robust and powerful with a simple yet intuitive interface that provides on-demand feedback to users. It also provides ways to exchange data with server-side languages and store it in databases without disconnecting the user from the application like standard applications do when refreshing the browser window.you will have the information needed to create fully functional Ajax applications.
6 comments:
What are the different frameworks available In AJAX?
A good framework is “Zephyr”.
It is used with php and seems to be very easy to use.
Prototype.JS Framework is available with detailed documentation, its very easy to handle AJAX and JavaScript, Introduce $ concept its very simple, For Ajax specially u don’t need to check cross broswer, Open, Close and error handling through traditional AJAX.
What are the limitations of AJAX?
Ajax is primarily a client/server technology. Client nodes in the web do not typically run web servers that can respond to HTTP GET and POST requests. Since clients cannot directly communicate with each other, any distributed application developed using
Ajax would require a central web server system to negotiate requests between clients. Client A could generate events/data for and respond to events/data from Client B however both would need to connect to a common web server to facilitate the communication.
Another limitation of Ajax is slow or unreliable network connections. Traditional web applications that require a full round-trip to the server may behave slowly for end users but they would be predictable. End users would generally intuitively
know they have performed an action, such as submitting a form or clicking a link, and must
wait for a server to respond. With Ajax, users have less intuition about which type of events within a page may result in a need to wait for a server response. Instead of enhancing the end user experience, Ajax over slow or unreliable network
connections may reduce usability if not carefully designed to accommodate both fast and slow network characteristics.
What is the difference between DOM Parser and AUX Parser?
In DOM parser is used at server side in php using domxml.
While AUX parser is used at client side in javascript
Post a Comment