Home arrow Web Standards arrow Configuring Servers and Databases with Chrome

Configuring Servers and Databases with Chrome

In this second part of a four-part article that explains how to prepare XUL Internet applications for a commercial setting, you'll learn how to configure servers and build a database. This article is excerpted from chapter four of Programming Firefox, written by Kenneth C. Feldt (O'Reilly, 2007; ISBN: 0596102437). Copyright © 2007 O'Reilly Media, Inc. All rights reserved. Used with permission from the publisher. Available from booksellers or direct from O'Reilly Media.

Author Info:
By: O'Reilly Media
Rating: 5 stars5 stars5 stars5 stars5 stars / 3
June 12, 2008
  1. · Configuring Servers and Databases with Chrome
  2. · The server-side response
  3. · When Things Go Wrong
  4. · Adding a Database
  5. · Creating account tables

print this article

Configuring Servers and Databases with Chrome
(Page 1 of 5 )

The client-side request

Firefox supports the XMLHttpRequest, which is generally modeled after Microsoft’s IXMLRequestdesign. We can use the request to retrieve either simple text strings, or XML fragments that may be parsed and passed to the interface document’s Document Object Model (DOM) structure.

To use the request, JavaScript scripts create an instance of anXMLHttpRequestobject to be sent to the server, passing the object a reference to a callback function to be invoked once the request is completed. The callback function then takes whatever action is determined by the response.

Table 4-1 summarizes the functions and properties of the XMLHttpRequestobject most relevant to us for the upcoming exercise.

Table 4-1. XMLHttpRequest methods and properties

Method/Property Description
open(sendMethod, sendURL, doAsync)


sendURL= query string.

doAsync= ifTRUE, return upon transmission of request.

.onreadystatechange Function called when the request’s “ready” state changes.
send(null) Sends the request to the server.
.readyState Monitored within the callback;code == 4signals that the request is completed.

Monitored within the callback;code==200signals that the server was successful in executing the request.


Accesses the text returned by the server to be parsed and processed in an application-specific format.


Accesses the text returned by the server when the text is presumed to consist of an XML document.

Before we start to code, we need to decide on a send/receive protocol between our client application and the server. We will use a very simple URL string to send commands to our server:


From our server, we will expect a comma-delimited string for a response:


We will expect the first value token to be a case-insensitivetrue|falsevalue to indicate the success of the command.

We will now change our newssearch.js file to implement a few modifications for our client/server model:

  • We will build a genericdoServerRequestfunction to build anXMLHttpRequest object and send it to the server. To support that function, we will also create acommandArgobject to hold name-value pairs of arguments that can be used to populate an array of arguments. The function will set theasyncflag in theopen function toTRUE, meaning that control will immediately return to the application once the request is sent.
  • We will change our login-button command handler to call the newly createddoServerRequestfunction.
  • We will change the logic to move successful and failed paths for login into separate functions.
  • We will write some JavaScript to add a callback function to interpret the response from the server and call the successful or failed login functions:

      function genericBtnHandler(event){
      try { // try block
      var infoString = "Type = " + event.type + ",";
      infoString += "Target = " + event.target + ",";
      infoString += "Target.tagName = " + event.target.tagName + ",";
      infoString += "Target.id = " + event.target.id + ".";
      dump(infoString + "\n");
      } // try block
      catch (e) {
    alert("genericBtnHandler exception: " + e);

      function doLogin(event) {

      try { // try
      var theArgs = new Array;
      theArgs[0] = new commandArg("un",document.getElementById("userName").value);
      theArgs[1] = new commandArg("pd",document.getElementById("password").value);
    } // try
       catch (e) { //
        alert("doLogin exception: " + e);
      // Dynamically assign our event handler properties
    function initialize() {
    try {
       // Add a login script
       catch (e) {
    alert ("Exception: " + e);

      function loginOK() {
       var theParent = document.getElementById("contentArea");

    != 0)

      // Now re-create a welcome area
       theParent.style.backgroundColor = "LightSeaGreen";
       theParent.style.borderColor = "gray";
       theParent.style.borderStyle = "ridge";
       var leftSpacer = document.createElement("spacer");
       var newDescription = document.createElement("description");
       var newDescriptionText = document.createTextNode("Welcome!");
       var rightSpacer = document.createElement("spacer");

      function commandArg(argKey,argValue) {
       this.key = argKey;
       this.value = argValue;

      function loginFail(){
       document.getElementById("msgDescription").childNodes[0].nodeValue =
    "User not authenticated.";
       document.getElementById("userName").value = "";
       document.getElementById("password").value = "";

      // CreateServerRequest
      var theServerRequest;
      // commandArgs is an array of arguments, each element
      // is converted into a PHP GET URL field
      function doServerRequest(commandString,commandArgs) {

       theServerRequest = new XMLHttpRequest();
       var theString ="http://localhost/ doCommand.php?"+"&command="+commandString+"&";
       for (var i = 0; i < commandArgs.length; i++) { // build remaining parameters
    theString += commandArgs[i].key + "=" + commandArgs[i].value ;
    if (i != (commandArgs.length-1)) theString += "&";
      } // build remaining parameters
      theServerRequest.onreadystatechange = retrieveServerResponse;


     function retrieveServerResponse() {
      if (theServerRequest.readyState == 4) { // all done
       // Check return code
    if (theServerRequest.status == 200) { // request terminated OK
         alert("Response is " + theServerRequest.responseText);
         if (theServerRequest.responseText == "retcode=true") { // all OK
         } // all OK
         else loginFail();
    } // request terminated OK
       else { // something is wrong
        alert("Response failed.");
       } // something is wrong
      } // all done

We wrote thedoServerRequestfunction to take an array of input arguments. The code then steps through the array to build a URL containing our completeGET request URL.

The request object calls theretrieveServerResponsefunction each time the state changes, and once it reaches"4"(a code that means the server has completed the request), it checks for a status of200(meaning the server successfully completed the request) and finally parses the text returned by the server to see whether the user is authenticated.

blog comments powered by Disqus

- Mozilla Popcorn Maker 1.0 Makes Videos More...
- Completing a Configuration for Chrome and a ...
- Getting Connected with Firefox and Chrome
- Configuring Servers and Databases with Chrome
- Configuring Firefox for Chrome and a Server
- Designing the Elements of a Web Page
- Matching div heights with CSS and JavaScript
- Forms
- Get Down With Markup
- If I Said You Had a Beautiful Body...
- Web Standards in Dreamweaver Part 3
- Web Standards in Dreamweaver, Part 2
- Web Forms
- Making Lists Using XHTML
- Web Standards in Dreamweaver, Part 1

Watch our Tech Videos 
Dev Articles Forums 
 RSS  Articles
 RSS  Forums
 RSS  All Feeds
Write For Us 
Weekly Newsletter
Developer Updates  
Free Website Content 
Contact Us 
Site Map 
Privacy Policy 

Developer Shed Affiliates


© 2003-2019 by Developer Shed. All rights reserved. DS Cluster - Follow our Sitemap
Popular Web Development Topics
All Web Development Tutorials