Solve the Page Waiting Game with Threaded AJAX

Solve the Page Waiting Game with Threaded AJAX

eople hate to wait. In fact, when it comes to a computer, they hate to wait more than about 200 milliseconds. This can be a problem when your Web-based application uses a process that takes many seconds or even minutes. You can’t just put up a progress dialog or a wait cursor.

Fortunately ASP.NET offers a few different solutions for handling such long-running processes, which vary depending on the level of interactivity required and the amount of complexity you are willing to handle. This article will start with a sample application to demonstrate the problem and run through two solutions: one using a simple polling technique, and the other a more advanced AJAX solution.

Be warned that there are some false steps to be found in the .NET framework. One in particular is the IAsyncHTTPHandler, which at first glance, looks like it will help with long web page requests. However, this asynchronous HTTP handler is designed to free up the processor when some task on a page takes some time but doesn’t require any CPU. A good example is making a Web request in the middle of a page. In this case the asynchronous HTTP handler is very efficient.

The Problem
For this article, I’ll be focusing on a different problem. In the sample application I have created a page that reports the current temperature, wind, and other weather elements for five different airports. It takes the web service about five seconds to get each data. So if I let the page run as shown in Figure 1 it takes almost a minute before the server returns a page?an unacceptable wait time for any user.

The HTML for the long-running page is shown in Listing 1. The page load event code creates a data set for the grid. Then it runs through the various airports and calls the web service to get the data. The method then stuffs the data from the web service into the data set and attaches it to the grid control (see Figure 2).

The WSDL for this web service is It defines a bunch of different methods, only one of which I’ll use: The getSummary method, which returns a block of data including the location of the airport, the wind, the sky conditions, the visibility, and more.

Figure 1. Waiting: The original sample applications takes almost a minute to load the page.
Figure 2. Basics: The Web service for the sample application performs a simple weather query.

Even a single request to this server takes a lot longer than a single page fetch should take. Another alternative is to have a thread run in the background to get the data, while pages on the front end monitor the output of the thread continuously.

Moving to Threads
A threading solution provides a much cleaner experience to the user because they get updates of the processing on a periodic basis. Those responses are easy to prepare so they come back instantly even though the processing in the background might take a while.

To handle the threading system I’ll use two classes and one interface. The JobHandler singleton maintains a set of objects that implement the IJob interface. The JobHandler manages the threads for the system. When a job is added a new thread is created and the Start method is called on the job within a new thread. An ID string is returned that can then be used to lookup the job later.

The UML for the system is shown in Figure 3.

Figure 3. Picture This: The screen shot shows the UML for the Job system.

The WeatherJob is an implementation of IJob that polls the weather from a specified set of airports and fills up a DataSet named Data that contains the weather reports.

The code for the JobHandler singleton is shown in Listing 2, which is pretty straightforward. The only interesting thing about it is the AddJob method that creates a new thread for the job and calls the Start method.

The interface for jobs is shown in Listing 3. The constructor sets up the data set for the job. And the Start method, through each of the airports, calls the web request and stores the returned data in the data set.

A Polling Solution
The first solution to monitoring the weather job is to use polling. To do that the page will post back to itself every two seconds. On the first page request the job will start. After that the page will monitor the output of the weather job by hooking up the data in the job to the data grid on the page. The relationship between the browser, the web server, and the thread is shown in Figure 4.

Figure 4. Polled: The polled HTML solution shows the relationship between browser, server, and thread.

The HTML for the polling page is shown in Listing 4. The interesting part is the script block within the refreshScript label. When the label is visible the script will execute to re-submit the form two seconds after the page loads. That will refresh the data in the grid.

The code behind for the polled HTML is shown in Listing 5. The import code here is in the page_load method. If the request ID that is stored in the hidden form field is null or blank then this is the first time the page is loaded. The first time the page is loaded the job is created and the ID of the job is placed in the hidden form field.

After two seconds the Javascript will fire and the page will reload. The second time around the request ID will come through the hidden input field and the code will find the job with the specified ID and use the data to populate the data grid.

The AJAX Solution
Page reloads in Internet Explorer cause an audible click and a flash as the page goes to white and waits to reload. This can be pretty annoying if it’s happening every two seconds. AJAX provides an alternative where there is only one page load and the Javascript on the page requests the status of the request every 500 milliseconds, updating the page dynamically (see Figure 5).

Figure 5. The AJAX Solution: Javascript updates the page data in the background every 500 milliseconds.

The HTML side of the AJAX page is shown in Listing 6. The majority of the code is in the Javascript. The Javascript starts with the invocation of the addField calls, which adds the different fields that are returned in the XML the server. The startup page starts the first request to the server. The getData starts a request by calling createHTTPRequest. This function has cross-platform code to build the HTTP request object.

The HTTP request is asynchronous. When it completes, the handleResponse function is called. That function parses up the XML and creates some new HTML for the data table. That HTML is placed into the ‘grid’


The code behind for this page is shown in Listing 7. The page_load of this code starts the job and then sets the hidden input field with the URL of the data request page.

The get_data.aspx page takes a request ID and returns an XML representation of the current data set. The page code is shown below:

get_data.aspx<%@ Page language="c#" Codebehind="get_data.aspx.cs"   AutoEventWireup="false" Inherits="background.get_data" %>

Obviously the code behind is more important in this case. That code is shown in Listing 8, which starts with setting the content type of the response to ‘text/xml.’ Without that the AJAX code in the browser won’t create an XML document from the response. After that the code gets the request and asks the DataSet to create the XML. It then alters the XML response slightly to add the ‘done’ field, which tells the client whether the request has completed.

When the page first launches it looks like Figure 6.

Figure 6. Still Polling: The screen shot shows the AJAX page while it is still polling.
Figure 7. Complete: The screen shot shows the completed AJAX page.

When the request has completed the browser will look like Figure 7.When working with AJAX solutions keep in mind that you are setting a minimum browser requirement when you write the code. Not all browsers can create an HTTP request. In fact, just the most recent browsers can do it. Ideally your solution should support both a polling version for older browsers and an AJAX version for newer browsers.

Caveat Emptor
Threading can be problematic at the best of times. And in this case the threading can be harder to monitor than usual because it’s running on the server in the background. It’s possible that the request will keep running even if there is no web client monitoring it. If that is an issue then you should have the web monitoring code set a time stamp with the threaded process. If the threaded process sees that it hasn’t been viewed for a while then it can cancel itself.

There are a number of ways to do background processing in .NET. This threading approach is just one way. You can also work with ASP.NET cache, or even go so far as to create a real background process.

With these different techniques you can make turn long processing wait times into a user experience that gives rich feedback about how the processing is going.


About Our Editorial Process

At DevX, we’re dedicated to tech entrepreneurship. Our team closely follows industry shifts, new products, AI breakthroughs, technology trends, and funding announcements. Articles undergo thorough editing to ensure accuracy and clarity, reflecting DevX’s style and supporting entrepreneurs in the tech sphere.

See our full editorial policy.

About Our Journalist