Publishers of technology books, eBooks, and videos for creative people

Home > Articles > Web Design & Development > Adobe AIR

  • Print
  • + Share This
This chapter is from the book

The XMLHttpRequest Object

The XMLHttpRequest object, which is part of JavaScript, has been around for years but has really gained popularity recently thanks to the rise of Ajax. XMLHttpRequest is a class that defines the functionality for HTTP (HyperText Transfer Protocol) interactions. Even if that sounds like gibberish to you, you're actually quite familiar with the concept: When you load a Web page in your browser, you're making an HTTP request (normally). Using XMLHttpRequest, JavaScript in one page can make that same kind of transaction behind the scenes (i.e., without the browser leaving the current page). The JavaScript can use the response from the second page as needed, most likely to update the first page's content in some way.

As an example of how you might use this, say you wanted to create an iTunes-like application with a search feature. The user enters some text—a song or album title, or an artist's name—in a box, and then clicks an icon or presses Enter. This would queue the JavaScript, which would use Ajax to send the search term to another page. That page would, unbeknownst to the user, actually perform the search and return the results to the original page. The JavaScript in that page would then update the application window, showing the results of the search.

There are many ways this kind of functionality can be added to an application by using the AIR API. But it's worth knowing how to make an XMLHttpRequest using plain old JavaScript, so let's work through an example.

To use XMLHttpRequest, start by creating an object of type XMLHttpRequest:

var xhr = new XMLHttpRequest();

Next, provide to the open() method the type of request to make—normally GET or POST—and the file to be communicated with:'get', 'filename.ext');

This line opens a connection to filename.ext, to which it will make a GET request. If you're not familiar with what GET and POST mean, search the Web for (probably too detailed) answers. Or, for the time being, simply understand that you'll generally use GET, because it's the standard method for requesting information from a page, whereas POST is used to send information to a page.

The next step is to name the function to be called when filename.ext returns its results. The onreadystatechange property takes this value. This property is one of five important XMLHttpRequest object properties listed in Table 4.1 (remember that in object-oriented programming a property or attribute is a variable defined in a class). Assign to this property the name of the function without any parentheses or quotation marks:

xhr.onreadystatechange = callThisFunction;

Table 4.1. Performing XMLHttpRequests relies upon the XMLHttpRequest properties listed here.

XMLHttpRequest Properties


Contains the...


Name of the function to be called when the readyState property changes


Current state of the request (see Table 4.2)


Returned data as a string


Returned data as XML


HTTP status code returned

So the JavaScript will send the request to filename.ext, that page will send back a reply, and at that time the callThisFunction() function will be called. This function, defined shortly, will take the returned data and update the page content accordingly.

The last step in this sequence is to send the request. For GET requests, you should provide the value null as the send() method's only argument:


That wraps up the "making the request" JavaScript; next is the handling of the returned results (what filename.ext sends back). Remember that this will be done within the callThisFunction() function. But you'll first want to confirm that the request was successful. To do so, check that the readyState is equal to 4 (see Table 4.2 for the list of readyState values):

function callThisFunction () {
    if (xhr.readyState == 4) {
       // Handle the returned data.

Table 4.2. Of the five readyState values listed here, the last one is the most important for knowing when to handle the returned data.

XMLHttpRequest readyState Values













The readyState attribute indicates the status of the request process. At first the ready-State value is uninitialized (which equals 0, see Table 4.2). When the request is made, the server page starts to load, making the readyState value 1. Then the server page finishes loading, making readyState 2. Some interaction will occur between the two pages, making readyState 3, and eventually the request is completed, giving readyState a value of 4. Often, these states will change very quickly, but in terms of handling the response, getting a readyState of 4 is most important.

Having created the XMLHttpRequest object, performed the transaction, and confirmed the results, the final step is to use the returned data to alter the page content. The easiest way to access that data is to refer to the responseText property. This attribute stores the result of the request, which is what the requested page would display if loaded directly in a Web browser. If the result of the request is XML data, you would use responseXML instead.

Once you have the page's response, you can use it however the application dictates. You might write the response content to the page, use it to change some existing values, and so on. To help demonstrate this concept and to provide you with some usable code, let's run through a basic example of an XMLHttpRequest.

To use XMLHttpRequest:

  1. Begin a new AIR project in your text editor or IDE.

    For this particular program, it's not necessary to include the AIRAliases.js file, although it's not a big deal if you do.

  2. Create a plain text file named message.txt that contains some text (Script 4.3).

    Script 4.3. This bit of a text (a quote from Homer Simpson, naturally) will be retrieved using an XMLHttpRequest.

    1   They have the Internet on computers now.

    The contents of this file will be read in by the XMLHttpRequest object and printed in the main application page.

  3. Within the body of the main HTML file, add the following (Script 4.4):
    <h1 id="response" style="color: red;"></h1>
    <button id="do" onclick="getMessage()">Get the message!</button>

    Script 4.4. This is the primary HTML file for the XMLHttpRequest AIR application. It performs the actual request, updating the body of the page using the results.

    1   <html><!-- Script 4.4 -->
    2      <head>
    3         <script type="text/javascript">
    5            // Create an XMLHttpRequest object:
    6            var xhr = new XMLHttpRequest();
    8            // This function is called when the user clicks the button:
    9            function getMessage() {
    11              // Open the connection:
    12    'get', 'message.txt');
    14              // Identify the function to handle the ready state change:
    15              xhr.onreadystatechange = printMessage;
    17              // Send the request:
    18              xhr.send(null);
    20           } // End of getMessage() function.
    22           // This function updats the page after the request is made:
    23           function printMessage() {
    25              // Only do something when the readyState is complete:
    26              if (xhr.readyState == 4) {
    27                 document.getElementById( 'response' ).innerText = xhr.responseText;
    28              }
    30           } // End of printMessage() function.
    32        </script>
    33     </head>
    34     <body>
    35        <h1 id="response" style="color: red;"></h1>
    36        <button id="do" onclick="getMessage()">Get the message!</button>
    37     </body>
    38  </html>

    The body of this application is just a button (Figure 4.10) that, when clicked, invokes the XMLHttpRequest functionality. That JavaScript will update this empty H1 with the response from the text file (Figure 4.11).

    Figure 4.10

    Figure 4.10 The application as it appears when it first opens.

    Figure 4.11

    Figure 4.11 The result after clicking the button.

  4. Within the head of the main HTML file, begin a section of JavaScript and create an XMLHttpRequest object:
    <script type="text/javascript">
    var xhr = new XMLHttpRequest();
  5. Define the getMessage() function:
    function getMessage() {'get', 'message.txt');
      xhr.onreadystatechange = printMessage;

    This function will be called when the user clicks the button (see the code in step 3). The first step within the function is to invoke the open() method of xhr (that variable is accessible within the function because it was defined outside of the function, per JavaScript scope behavior). The first argument is the HTTP method to use and the second is the name of the file to request, which in this case is message.txt, created earlier.

    Next, assign to the onreadystatechange attribute the name of the function to be called when the readyState value changes. Finally, make the request by calling send().

  6. Define the printMessage() function:
    function printMessage() {
      if (xhr.readyState == 4) {
         document.getElementById( 'response' ).innerText = xhr.responseText;

    This function will be called whenever the readyState value changes (it will actually change several times). The code in this function will not do anything until readyState has a value of 4. At that time, the innerText—the value between the tags—of the H1 with an ID of response will be assigned the value of the textual response of message.txt. This will literally be the contents of that file (see step 2).

  7. Complete the JavaScript section:
  8. Save, test, debug, run, and build the application.

    Make sure that the message.txt file is in the same directory as index.html and that it's included when you build the application.

  • + Share This
  • 🔖 Save To Your Account

Peachpit Promotional Mailings & Special Offers

I would like to receive exclusive offers and hear about products from Peachpit and its family of brands. I can unsubscribe at any time.


Pearson Education, Inc., 221 River Street, Hoboken, New Jersey 07030, (Pearson) presents this site to provide information about Peachpit products and services that can be purchased through this site.

This privacy notice provides an overview of our commitment to privacy and describes how we collect, protect, use and share personal information collected through this site. Please note that other Pearson websites and online products and services have their own separate privacy policies.

Collection and Use of Information

To conduct business and deliver products and services, Pearson collects and uses personal information in several ways in connection with this site, including:

Questions and Inquiries

For inquiries and questions, we collect the inquiry or question, together with name, contact details (email address, phone number and mailing address) and any other additional information voluntarily submitted to us through a Contact Us form or an email. We use this information to address the inquiry and respond to the question.

Online Store

For orders and purchases placed through our online store on this site, we collect order details, name, institution name and address (if applicable), email address, phone number, shipping and billing addresses, credit/debit card information, shipping options and any instructions. We use this information to complete transactions, fulfill orders, communicate with individuals placing orders or visiting the online store, and for related purposes.


Pearson may offer opportunities to provide feedback or participate in surveys, including surveys evaluating Pearson products, services or sites. Participation is voluntary. Pearson collects information requested in the survey questions and uses the information to evaluate, support, maintain and improve products, services or sites; develop new products and services; conduct educational research; and for other purposes specified in the survey.

Contests and Drawings

Occasionally, we may sponsor a contest or drawing. Participation is optional. Pearson collects name, contact information and other information specified on the entry form for the contest or drawing to conduct the contest or drawing. Pearson may collect additional personal information from the winners of a contest or drawing in order to award the prize and for tax reporting purposes, as required by law.


If you have elected to receive email newsletters or promotional mailings and special offers but want to unsubscribe, simply email

Service Announcements

On rare occasions it is necessary to send out a strictly service related announcement. For instance, if our service is temporarily suspended for maintenance we might send users an email. Generally, users may not opt-out of these communications, though they can deactivate their account information. However, these communications are not promotional in nature.

Customer Service

We communicate with users on a regular basis to provide requested services and in regard to issues relating to their account we reply via email or phone in accordance with the users' wishes when a user submits their information through our Contact Us form.

Other Collection and Use of Information

Application and System Logs

Pearson automatically collects log data to help ensure the delivery, availability and security of this site. Log data may include technical information about how a user or visitor connected to this site, such as browser type, type of computer/device, operating system, internet service provider and IP address. We use this information for support purposes and to monitor the health of the site, identify problems, improve service, detect unauthorized access and fraudulent activity, prevent and respond to security incidents and appropriately scale computing resources.

Web Analytics

Pearson may use third party web trend analytical services, including Google Analytics, to collect visitor information, such as IP addresses, browser types, referring pages, pages visited and time spent on a particular site. While these analytical services collect and report information on an anonymous basis, they may use cookies to gather web trend information. The information gathered may enable Pearson (but not the third party web trend services) to link information with application and system log data. Pearson uses this information for system administration and to identify problems, improve service, detect unauthorized access and fraudulent activity, prevent and respond to security incidents, appropriately scale computing resources and otherwise support and deliver this site and its services.

Cookies and Related Technologies

This site uses cookies and similar technologies to personalize content, measure traffic patterns, control security, track use and access of information on this site, and provide interest-based messages and advertising. Users can manage and block the use of cookies through their browser. Disabling or blocking certain cookies may limit the functionality of this site.

Do Not Track

This site currently does not respond to Do Not Track signals.


Pearson uses appropriate physical, administrative and technical security measures to protect personal information from unauthorized access, use and disclosure.


This site is not directed to children under the age of 13.


Pearson may send or direct marketing communications to users, provided that

  • Pearson will not use personal information collected or processed as a K-12 school service provider for the purpose of directed or targeted advertising.
  • Such marketing is consistent with applicable law and Pearson's legal obligations.
  • Pearson will not knowingly direct or send marketing communications to an individual who has expressed a preference not to receive marketing.
  • Where required by applicable law, express or implied consent to marketing exists and has not been withdrawn.

Pearson may provide personal information to a third party service provider on a restricted basis to provide marketing solely on behalf of Pearson or an affiliate or customer for whom Pearson is a service provider. Marketing preferences may be changed at any time.

Correcting/Updating Personal Information

If a user's personally identifiable information changes (such as your postal address or email address), we provide a way to correct or update that user's personal data provided to us. This can be done on the Account page. If a user no longer desires our service and desires to delete his or her account, please contact us at and we will process the deletion of a user's account.


Users can always make an informed choice as to whether they should proceed with certain services offered by Adobe Press. If you choose to remove yourself from our mailing list(s) simply visit the following page and uncheck any communication you no longer want to receive:

Sale of Personal Information

Pearson does not rent or sell personal information in exchange for any payment of money.

While Pearson does not sell personal information, as defined in Nevada law, Nevada residents may email a request for no sale of their personal information to

Supplemental Privacy Statement for California Residents

California residents should read our Supplemental privacy statement for California residents in conjunction with this Privacy Notice. The Supplemental privacy statement for California residents explains Pearson's commitment to comply with California law and applies to personal information of California residents collected in connection with this site and the Services.

Sharing and Disclosure

Pearson may disclose personal information, as follows:

  • As required by law.
  • With the consent of the individual (or their parent, if the individual is a minor)
  • In response to a subpoena, court order or legal process, to the extent permitted or required by law
  • To protect the security and safety of individuals, data, assets and systems, consistent with applicable law
  • In connection the sale, joint venture or other transfer of some or all of its company or assets, subject to the provisions of this Privacy Notice
  • To investigate or address actual or suspected fraud or other illegal activities
  • To exercise its legal rights, including enforcement of the Terms of Use for this site or another contract
  • To affiliated Pearson companies and other companies and organizations who perform work for Pearson and are obligated to protect the privacy of personal information consistent with this Privacy Notice
  • To a school, organization, company or government agency, where Pearson collects or processes the personal information in a school setting or on behalf of such organization, company or government agency.


This web site contains links to other sites. Please be aware that we are not responsible for the privacy practices of such other sites. We encourage our users to be aware when they leave our site and to read the privacy statements of each and every web site that collects Personal Information. This privacy statement applies solely to information collected by this web site.

Requests and Contact

Please contact us about this Privacy Notice or if you have any requests or questions relating to the privacy of your personal information.

Changes to this Privacy Notice

We may revise this Privacy Notice through an updated posting. We will identify the effective date of the revision in the posting. Often, updates are made to provide greater clarity or to comply with changes in regulatory requirements. If the updates involve material changes to the collection, protection, use or disclosure of Personal Information, Pearson will provide notice of the change through a conspicuous notice on this site or other appropriate way. Continued use of the site after the effective date of a posted revision evidences acceptance. Please contact us if you have questions or concerns about the Privacy Notice or any objection to any revisions.

Last Update: November 17, 2020