On 2006-11-06, Miguel Figueiredo Mascarenhas Sousa Filipe wrote:
On 11/5/06, Matthew Dillon <[EMAIL PROTECTED]> wrote::Is this kind of change something that can be done just by changing :the server's config files? Or would it involve rewriting code? It's pretty basic to the design of the http server. Apache is a fairly heavy weight web server. I'm sure you can find lighter-weight servers to serve out static content. There is really no need to go to such extremes unless you are actually running a busy site. On busy sites it is often a very good idea to separate the static content out from thedynamic content and to serve the static content from a different machineentirely.lighttpd comes to mind.. very good for static content, and it uses the mentioned arquitecture (1 main thread + kqueue/poll)... http://www.lighttpd.net/
If you're using Ruby on Rails, Zope, Django, TurboGears, or even recent versions of PHP, you can run those as FastCGI servers. Which means your static content is served by lighttpd and dynamic content is generated and served by a different process. Since the process never dies, it can maintain database connections and cache things in-memory. lighttpd has built-in FastCGI support.
