"Srinivas Moorthy" <sr**************@hotmail.com> wrote in message
news:05****************************@phx.gbl...
Hi
The best solution according to me is just Flush some
content to the browser. You can use Response.Flust.
Let me give an classic example on this. For example if
your page is having some listing of records which is of
thousands or mroe than that.. flush for every 100 records
to the browser. For this the Buffer to be On. I think
in .Net the Buffer is ON by default.
I don't think this will help much, as asp.net will only generate html
in one of the later stages of processing (render phase). If a lot
of work is done in "load" or "prerender", then a buffer setting
will have no effect.
If you are not clear please go through the Response.Buffer
example.
thanks
srinivas moorthy-----Original Message-----
When request is initiated at the client system, the Web
Server may take tens of second to couple of minutes,Mean while user gets annoyed and cliks Refresh Button
several times."Is it Possible to know Response time of the web server
before it starts work on Request.?"So that the user can be notified about the Progress.
.
There is no general way to get an expected response time
for a page. However, you as the developer of that page will
know at least that it will take a long time, and maybe you can even
make a guess how long this particular call will take (*you*
know what processing needs to be done).
What you could try do is a two step approach:
The link the user click on doesn't lead to the process page
but to an intermediate page. This page makes a guess how long
the real processing will take and tells that to the user (along with
some "I'm busy" graphic). Then that page will automatically
redirect to the real process page.
Hans Kestng
