I was just going to post that url to the guide also... But another option
I've come up with not listed in the guide is to use the *nix "at" command.
If I need to run some processor intensive application that doesn't need
apache_anything, I'll do a system call to "at" to schedule it to run
(usually I pass in "now"). However, the drawbacks are that it's a
complete seperate process and passing complicated structures isn't worth
the time to think about using at.
Jay
On Wed, 4 Oct 2000, Geoffrey Young wrote:
>
>
> > -----Original Message-----
> > From: David E. Wheeler [mailto:[EMAIL PROTECTED]]
> > Sent: Wednesday, October 04, 2000 3:44 PM
> > To: [EMAIL PROTECTED]
> > Subject: Forking in mod_perl?
> >
> >
> > Hi All,
> >
> > Quick question - can I fork off a process in mod_perl? I've
> > got a piece
> > of code that needs to do a lot of processing that's unrelated to what
> > shows up in the browser. So I'd like to be able to fork the processing
> > off and return data to the browser, letting the forked process handle
> > the extra processing at its leisure. Is this doable? Is forking a good
> > idea in a mod_perl environment? Might there be another way to do it?
>
> http://perl.apache.org/guide/performance.html#Forking_and_Executing_Subproce
> ss
>
> the cleanup phase is also a good place to do extended processing. It does
> tie up the child until the processing finishes, but it at least make the
> client think that the response is finished (so that little moving thingy in
> netscape stops moving around)
>
> HTH
>
> --Geoff
>
> >
> > TIA for the help!
> >
> > David
> >
> > --
> > David E. Wheeler
> > Software Engineer
> > Salon Internet ICQ: 15726394
> > [EMAIL PROTECTED] AIM: dwTheory
> >
>
