[Javascript] Question - Page Load Feedback

[Flavio Gomes]

Tim, here on our PHP applications we "echo" some data, like the 
"percentage of completion" for long time operations to prevent the 
browser from timingout (I just got myself a new verb)

Yes, it looks pretty ugly:
 Processing Contract Number 4112556... ( 2% Completed)
 Processing Contract Number 4112557... ( 4% Completed)
 Processing Contract Number 4112558... ( 6% Completed)
 Processing Contract Number 4112559... ( 8% Completed)

-- 
Flavio Gomes
flavio at economisa.com.br



Mike Dougherty wrote:

> Our intranet runs on a dedicated IIS server - we just turned the 
> timeouts up.
>
> We don't use xmlhttp on our intranet - didn't know about that when we 
> built it.  We just have ASP sending SQL requests via ADO that wait for 
> the data from the DB then output html.  Some of the later 
> dhtml-inspired activities use client-side ADO to talk directly from 
> the browser to the SQL server.  If I had it to do over, I would be 
> using xmlhttp and not forcing those forms into IE only (ADO activeX) 
> and inherent security & scalability problems.
>
> On Thu, 21 Jul 2005 00:26:11 +0800
>  Timothy White <weirdit at gmail.com> wrote:
>
>> On 7/20/05, Mike Dougherty <mdougherty at pbp.com> wrote:
>>
>>> I didn't think the page was reloading.  I thought a content div was 
>>> being repopulated by an
>>> xmlhttp call result.  It would be a good idea to have "normal" pages 
>>> indentify that you were
>>> leaving them when going to a slow-loading next page.  I might employ 
>>> the strategy you're
>>> describing on the next modification of our intranet site.  (we 
>>> sometimes launch data-intensive
>>> applications that take 10-15 minutes before the page returns - the 
>>> user is looking at the old page
>>
>>
>> How do you keep the page timing out? Unless your using xmlhttp
>> requests with return handlers?? IIRC most servers timeout after 5
>> minutes, the browser usually times out after 1.5 minutes of no data.
>>
>> Tim
>