|
|
Posted by Paul Fisch on 01/07/08 08:19
On Jan 7, 2:14 am, Gilles Ganault <nos...@nospam.com> wrote:
> On Sun, 6 Jan 2008 23:33:37 -0800 (PST), Paul Fisch <fis...@gmail.com>
> wrote:
>
> >> it really depends on your setup...whether or not php is being run as a
> >> module or as a cgi, what webserver you're using - it's the webserver
> >> software that can control this.
>
> >Do you know where I could go or what terms I should search to find out
> >more about this.
>
> I'm also interested in how to handle long-running PHP processes.
>
> Not sure if this is true, but here goes anyway:
> - the server and/or the browser usually time out after 30 seconds
> (HTTP protocol?), so the PHP script must regularly send some data to
> keep the pipes open
> - if the browser is closed, the PHP process will still run unless you
> put some code that checks for this, and aborts if the connection was
> closed
> - generally speaking, LAMP is not a good choice for long-running
> tasks. You might want to use other tools for this
Using the command set_time_limit(some #) can extend the timeout limit
to whatever you want.
Why isn't LAMP a good choice for long-running tasks?
Navigation:
[Reply to this message]
|