Asynchronous Wait State Pattern in ASP.NET

Putting a browser UI on business applications makes them easily accessible to users in remote locations, but it presents some challenges for the developer. One of those challenges is how best to construct it for a long-running process.
  For example, when a user enters data into a Web Form and clicks the submit button, the page does not change and the UI is unresponsive until the server sends a new page to the browser. If the UI is unresponsive for more than a few seconds, users are inclined to press the submit button repeatedly. These multiple submissions can cause problems for the application, forcing the developer to write code to handle the repeats.
  A cleaner approach would be to keep the user informed about the server process with updated messages and a progress bar in the browser. In this column, you will learn how to create an asynchronous ASP.NET wait page that does exactly that. Let's begin by creating a page that initiates a long-running process. (The samples in this article are written in C# unless otherwise noted.)

1 Comment

Comments have been disabled for this content.