Re: build's html page - refresh rate

What about something like this:

main build page (index.html):

<meta http-equiv="refresh" content="0; URL=log1.html">

log1.html:

<meta http-equiv="refresh" content="10; URL=index.html">

Then you put the actual content into log1.html the first time. It will 
periodically bounce to index.html and back.
Then when generating another version of the page you put it into 
log2.html, but only update index.html to point to log2 when the page 
write is complete.
Then hopefully since it is a small write to index.html it will never get 
a broken index.html, and will only update to the new page when its ready
(you could bounce backwards and forwards between log1 and log2)

Just an idea, I haven't tried it

David

Vladimir Glazounov wrote:

> Hi,
>
> there is no communication between perl & browser. Browser blindly 
> loads the page, no matter if it's complete or not. So, the different 
> location will not help. Or you have an idea how to tell the browser 
> that the page is written and to tell perl, that the page is being loaded?
>
> Vladimir
>
> David Fraser wrote:
>
>> Vladimir Glazounov wrote:
>>
>>> Hi,
>>>
>>> I would like to minimize status page fails. So I think, I add a 
>>> switch "--html_upd_rate" for page generation/update, and a 
>>> possybility to set a refresh rate in html page itself. With 
>>> generation is everything clear, but refresh rate once changed should 
>>> be stored somewhere. And not only for one session. So I thought 
>>> about cookies.
>>> Now I would like to know - do we need that feature at all? If yes, 
>>> are the cookies OK or there are some better alternatives?
>>> Best regards,
>>>
>>> Vladimir 
>>
>>
>>
>> Hi Vladimir
>>
>> What about outputing the new page to a separate file, and only 
>> telling the main page to reload once the separate file has finished 
>> writing? That might be a simpler way of avoiding failures entirely
>>
>> Cheers
>> David
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: [email protected]
>> For additional commands, e-mail: [email protected]
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [email protected]
> For additional commands, e-mail: [email protected]
>