Re: Looking for ways to prevent timeout

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Nathan Nobbe wrote:
> On 11/5/07, Jochem Maas <jochem@xxxxxxxxxxxxx> wrote:

...

yes yes yes to all that, except for one thing. Im personally of
the opinion such 'import' operation should involve no human interaction
and garanteed to complete (e.g. auto resume), save for possibly
initializing a process. the way I see it you what to try to garantee the
import will be atomic in such cases.

there is nothing to stop you having a fancy UI that polls the server
to check the job table (as exampled earlier in this thread) for the status
of a job (and subsequently, possibly retrieve some processed output).

the two processes ('init & 'review and 'run job') should be independent, any
form of control (e.g. a cancellation) should happen via some sort of IPC
mechanism and should be optional apart from possibly initialization (depending
on business requirements). successful import completion should not have to
rely on the user having to press 'continue' or even stay on the page or anything
of that nature.

also consider that with regard to such tasks it's not efficient to
have some one staring at a progress bar. and annoying, after a few seconds,
for the user, regardless of how pretty.

> 
> -nathan
> 

-- 
PHP General Mailing List (http://www.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php


[Index of Archives]     [PHP Home]     [Apache Users]     [PHP on Windows]     [Kernel Newbies]     [PHP Install]     [PHP Classes]     [Pear]     [Postgresql]     [Postgresql PHP]     [PHP on Windows]     [PHP Database Programming]     [PHP SOAP]

  Powered by Linux