ansaurus

Question

Answer 1

+1 A:

You can trigger a GIF animation on the client side, the moment you dispatch a request.

EFraim 2009-07-17 07:58:23

That wouldn't show a real time progress bar.

Andrew Siemer 2009-07-17 08:02:01

That's right. But most of progress bars are not real time. They are mostly indications of "action in progress, be patient." Though there are some exceptions such as file upload in GMail, which is based on Flash IMHO.

EFraim 2009-07-17 09:34:57

+1 A reasonable pragmatic solution.

AnthonyWJones 2009-07-17 15:35:35

Answer 2

A:

You won't be able to do this with just one asp page. You will need a page that is shown to the user (where you progress bar lives). Then you will need to make an ajax call (with jQuery??) in a loop to a page that reads a session object. And you will need a page that is actually doing your processing and writing it's status to the session that is being periodically monitored by the ajax call. You will need to make periodic calls with the ajax to check the session over time until you reach the final result. You could store a number in the session say 1-100 if it is a really long slow process...but 10, 20, ..., 100 would probably work best. When you get to 100 you would break the loop and no longer poll the session reading page.

The reason for this is that you need a page to display to the user for your bar.

The page that is doing the processing can't show anything to the user until it is done processing.

The page that simply reads the session can process quickly and show its results quickly.

Make sense?

Andrew Siemer 2009-07-17 08:01:09

Answer 3

+1 A:

There used to be a trick with either disabling the Response.Buffer (set it to false) or let it be buffered, but from time to time you do Response.Flush as you want to update your progress.

So, say you have your progress bar somewhere on top portion of your page (either image or table or div or whatever you want) and as you do something in asp script (say in a loop), from time to time, flush a javascript back to the client to update the progress bar that should already be on the screen. something like:

<%
  REM Might be a good idea to set the timeout to some large number here...
  Response.Timeout = ...
%>
<html>
:
<body>
  <p>Please wait...<span id="progress">0</span>% completed.</p>
  : content here...
  <%
  REM Make sure the things above this get sent to the client first
  REM so they will be rendered before the rest of the page is rendered.
  Response.Flush()

  For iCnt = 0 To 100
    REM Do some stuffs here...

  %>
    <script>$("#progress").html(i)</script>
  <%
    Response.Flush()
  Next
  %>
  : some more contents here...
</body>
</html>

I'm not sure if this still works with modern browsers, haven't use it in a while.

Jimmy Chandra 2009-07-17 08:19:21

Yikes! I haven't seen a REM statement in years. ;)

AnthonyWJones 2009-07-17 15:01:08

LOL, I haven't been in vb / vbscript world since .NET :) even during ASP day I prefer to write my server script using jscript instead near the end :).

Jimmy Chandra 2009-07-17 16:03:29

i tried this out and it worked for me fine i will try to write it in jscript ( i think this wont be a problem ) and then to merge it with my asp code.Thank you

OemerA 2009-07-19 20:07:15

Answer 4

A:

You are on the right track that the problem is that you are developing on Windows XP and running into the limitation that IIS 5 will only process one request at a time.
As you suspect the AJAX request for the progress is not returning until the original request that you are trying to monitor is finished.

There is no way around this that I know of with this version of IIS. It is likely another limitation built in to prevent you from using XP IIS 5 in a production environment. Even if a second request is coming from another machine with a different ip address it will not be processed until the first is complete.

pflunk 2009-07-17 20:12:54

Thank you i think you are right but i tried to do open the process.asp in firefox and the sessionreader.asp in IE in it works fine.In my desperation i wrote the status in a file and read it with the sessionreader.asp ( i know its a horrible workaround ) It works but if want to open both files (process.asp and sessionreader.asp) i get an answer from sessionreader.asp when process.asp is done.Thats why i think its Session based queue.

OemerA 2009-07-18 11:13:07

ansaurus

tags:

views:

answers:

Loading bar with classic asp

related questions