Thanks Eric for the reply.So, is it possible to run PHP in Apache, with each client-request being serviced in a different thread (and not a new-process-per-new-request)? Because, it is a well known fact that a process is a much-higher
Please, I must say at the outset that I am not in favour, or against any technology, but just wish to gauge some inputs on Apache internals, from the Apache experts :)If not, Apache-Tomcat looks to be clear winner over PHP-in-Apache (please correct me if I am wrong) :)entity than a thread.
--On Fri, Aug 9, 2013 at 9:57 PM, Eric Covener <covener@xxxxxxxxx> wrote:
It's not a point of differentation. You can run either technology manyOn Fri, Aug 9, 2013 at 11:57 AM, Ajay Garg <ajaygargnsit@xxxxxxxxx> wrote:
> Hi all.
>
> I was just doing some rudimentary research on what would be the best
> solution to implement server-side operations of our webapp.
> The "servlet" and "PHP" seem two widely used solutions.
>
>
> However, there is one important thing that struck me.
>
> Looking at http://www.tutorialspoint.com/servlets/servlets-life-cycle.htm,
> it states that every new client-request to a servlet, spawns a new thread.
> On the other hand, looking at
> http://php.net/manual/en/internals2.structure.lifecycle.php, it states that
> the Apache module MIGHT map different requests to a single process (with the
> CGI model DEFINITELY using the one-process-per-request implementation).
>
> Looking at the above, it seems that using Apache Tomcat to host a servlet,
> is better than running a PHP module in Apache (as far as
> resource-requirements are concerned at the server).
>
> Is my understanding correct?
different overlapping ways.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@xxxxxxxxxxxxxxxx
For additional commands, e-mail: users-help@xxxxxxxxxxxxxxxx
Regards,
Ajay
|