| Pure HTML Progress Bar | ||
|
||
|
This example shows how to show a Pure HTML Progress Bar during an upload. It assumes that minimal configuration settings in the web.config file are implemented.
|
| ASP | |
|
| progressupload.aspx | ||
|
Our multipart HTML form contains one file field for upload and one text field. The form action takes a URL which contains a Unique ID used to identify the transfer. It is this ID which allows the progress bar to connect with the uploading page. When the form is submitted we will need to submit both the data in the main window and also spawn off a separate window to track progress. So instead of using a standard submit button we use a normal button with a client side JavaScript attached to it. When the submit button is clicked the DoUpload client side function takes over. Before it allows the form to be submitted it takes the Unique ID - used to identify the transfer - and spawns a progress window (progressbar.aspx) putting the ID into the URL so that it can be picked up later. This is an unusual use of HTTP and worth reiterating. The progressbar.aspx page has an ID supplied to it via the URL (i.e. a GET request). The progressupload.aspx page has the content of the form submitted to it via a standard POST and also has an ID supplied via the URL. [C#] [VB] For the upload processing section we'll make use of some advanced ABCUpload features designed for the efficient processing of very large uploads. We start by creating an Upload object and check that we've received an uploaded file. If there's no file the most likely cause is that the client is requesting the form rather than uploading a file. If we have a file we check to see if the file data has been cached as a temporary file. This type of caching will only occur if the GigUpload functionality is enabled. If the file has been cached and it's not in an encoded format we detach it from the upload and move it wherever we want it to go. This avoids having two copies of a file on disk and it is also much faster if you are dealing with very large files. If the file hasn't been cached or it's in an encoded format we use the SaveAs method to save the file to disk. This will be less efficient than a move operation if the uploaded data is many hundreds of MB in size. Finally we report the file name using the properties associated with the Upload object and we report the contents of our text field using the standard ASP.NET Form collection. [C#] [VB]
|
| ASP | |
|
|
| progressbar.aspx | ||
|
The progress bar is slightly more complicated. We insert meta-tags to ensure that it refreshes itself every couple of seconds. We create a Progress object and set the ID to the Unique ID we were passed in the URL. This synchronizes the Progress object with the matching upload. We want to close the progress window once the transfer has been completed so we put in a simple piece of client side JavaScript to do this. The rest of the form simply reports to the user the information retrieved via the Progress object. The progress bar itself is simply a table containing a colored cell of a particular width. [C#] [VB]
|
| ASP | |
|
|
| global.asax | ||
|
In some situations you may wish to pick up progress events from within a global.asax file. The progress database is stored in Application Scope and if your progress bar and upload page are being served from different web applications they may become disassociated from each other. This is not a normal situation but it can occur for some web site designs. The most common situation in which this may occur is when operating from a web farm. In this scenario a page may be served from any one of a number of machines. So your upload page may be processed by one server while your progress bar is being served from another. In this situation you may wish to store the upload state in an external store such as a database. This way you can code your progress bar to retrieve upload state from your shared store rather than from the standard Progress object. In order to do this you need to pick up the progress update events which are sent out by ABCUpload and use them to update your shared store. You can do this using a handler within the global.asax file. The particular form of shared store you want to use dictates how your code should be written. The example below is an illustrative example designed to show how a handler can be coded. It simply makes a log of all the progress events which are received. [C#] [VB]
|