Playing devil's advocate here.
If php forked, that would mean that apache forked off a child that forked off a child.
So if the child at the end of the chain freezes, won't that confuse apache?
Threading might be nicer, but the same argumenet might hold.
But this is assuming that php is a webserver language, i.e. php-gtk
On Fri, May 11, 2001 at 10:10:00AM -0500, Jason Greene wrote:
> What do you guys think about having fork, waitpid, and signal handling available in
>php?
> I wrote a few simple fork test functions, and everything seemed to work fine.
>
> I am thinking that with sockets, shm, signals, and fork capability, there could
> be the possibility of someone writing daemons in php : )
>
> Can anyone think of possible problems that could occur in supporting this
>functionality?
> If it were to be added, where should it be added? IMO this type of thing probably
> shouldn't exist in ext/standard.
>
> Thanks,
> -Jason
>
>
>
>
> --
> PHP Development Mailing List <http://www.php.net/>
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
> To contact the list administrators, e-mail: [EMAIL PROTECTED]
>
--
PHP Development Mailing List <http://www.php.net/>
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
To contact the list administrators, e-mail: [EMAIL PROTECTED]
