On 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? It's not a point of differentation. You can run either technology many different overlapping ways. --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscribe@xxxxxxxxxxxxxxxx For additional commands, e-mail: users-help@xxxxxxxxxxxxxxxx
|