> Hi there,
>
> > > > >Uh, how about threads. I know that you don't need them much but
> > > > >it sure would be nice to be able to do background processing.
> > > >
> > > > PHP doesn't support threads?
> > >
> > > Nope...
> > >
> > > I've always thought of Forking as
> > > > overkill where threads are light and elegant.
> > >
> > > Depends on your environment... Forking in Linux is fairly lightweight.
> >
> > But when you are using php with a web server you can't really use the
> > process contol functions safely. Forking apache processes on your own
is
> > not a good idea. If forking were an option with php/apache it would do
just
> > fine. But currently it is not a viable solution.
>
> Web applications should NEVER fork processes or create their own threads.
> Period. Do this isn't safe in any environment, os, web server or
development
> tool. You can see on the J2EE specs that Servlets and EJBs are expressly
> prohibited from doing this.
Is this true? I know lots of servelet developers (mostly using Tomcat) that
do this all the time without encountering any problems. Could you point me
to the part in the spec where it indicates that this is inappropriate?
