From: "\"henq\" <henq _ replace 0 by o" <hvtijen@...0tmail.c0m>
Date: 2003-05-08T06:05:49+09:00
Subject: Re: Why is PHP so popular?  What can we learn from the PHP camp?


I beg to differ. You get many requests per second. So you need a thread or
process mechanism to let each request get its response when the response is
calculated/assembled/generated.

Apache happens to do just that *very* efficiently, by spawning off
processes. MySQL connections are pooled by the way (transparently for the
developer, if you want).

Monolithic apps have disadvantaged too, you know. For example, if they
crash, the whole app crashes, not just one script in a remote corner of the
web application.

From a computer sciences point of view app servers are the greatest, but in
real life, the mod_* / apache combo's are hard to beat.

~h


"Rasputin" <rasputin@shrike.mine.nu> wrote in message
news:20030507141127.GA50159@shrike.private.submonkey.net...
> * Brian Candler <B.Candler@pobox.com> [030506 11:34]:

>
> IMO, ruby appservers are the way to go, rather than a CGI-based approach
> have persistent objects on the server, and spawn a new thread for each
client.
> The servlet model is A Good Thing for OOP code, as opposed to a
> 'when the client connects fork off a shell with this in' legacy approach.
>
> -- 
> Rasputin :: Jack of All Trades - Master of Nuns
>