How to prevent a web client from timing out

[Alexis Iglauer]

The job is different every time, so a cron solution wouldn't work.  The
problem is that when the client times out the server kills the python
process doing the number crunching, so it can't mail the result to the user
either (that is a good idea though, hadn't thought of that).

So how do I stop apache from killing the process?  How well does xmlrpc work
in the real world?

Thanx
Alexis

The problem I seem to have is that
"Jeff Bauer" <jbauer at rubic.com> wrote in message
news:393BCA8B.FC062262 at rubic.com...
> Alex,
>
> One solution would be to run your number-crunching
> in a separate process (e.g. xmlrpc server) that
> your cgi script accesses.
>
> Jeff Bauer
> Rubicon Research
>
> aiglauer wrote:
> > I have written a number-crunching app in python. which is being
> > accessed on our intranet.  All pages generated on-the-fly in python.
> > Some of the calculations can take a while though (calc time anything
> > from 5secs to 30 minutes) and I get the client timing out and the
> > server will then kill the calculation process.
> >
> > Can I rig it so that the calculation process will still complete and
> > write its output to a file so that I can use it later?  (Writing to a
> > file is not a prob - preventing the thing getting slapped is).
>