Processing XML Data from AJAX Responses with JavaScript
Developing AJAX-driven applications can be an educational experience, particularly for those web developers who are taking their first steps into this exciting area. However, on the other hand, it can also be hard, specifically when it comes to deciding which output format should be used for delivering the results of AJAX-based http requests to end users. This article offers one sensible approach.
Processing XML Data from AJAX Responses with JavaScript - Assembling the different modules of the AJAX application (Page 4 of 4 )
Indeed, the best way to finish this article is by listing the complete source files that comprise this sample AJAX application. In this way you can see more clearly how each of these files interact with each other.
That being said, here are the full signatures for the two files that compose the mentioned AJAX application:
(definition of sample_ajax.htm file)
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
That's all for the moment. As I said before, you're completely free to introduce your own modifications to all the code samples included in this article, so you can be better prepared to implement different approaches for parsing AJAX responses. Happy coding!
Final thoughts
It's hard to believe, but this is actually the end of the series. Hopefully, this group of tutorials will be quite useful to you for demonstrating how to implement different methods for parsing AJAX responses with JavaScript, whether these ones are served as plain text or in XML format.
See you in the next web development tutorial!
DISCLAIMER: The content provided in this article is not warranted or guaranteed by Developer Shed, Inc. The content provided is intended for entertainment and/or educational purposes in order to introduce to the reader key ideas, concepts, and/or product reviews. As such it is incumbent upon the reader to employ real-world tactics for security and implementation of best practices. We are not liable for any negative consequences that may result from implementing any information covered in our articles or tutorials. If this is a hardware review, it is not recommended to open and/or modify your hardware.