On Sun, Sep 25, 2011 at 1:28 PM, Valery Reznic <valery_rez...@yahoo.com>wrote:
> I am tempted to try :) > > What do you think is better Nginx or lighttpd? > Last time I tried lighttpd, it was a pain over time. It did work, but its memory consumption has been growing. Searching on the net shows memory leaks to be a Known Issue (TM) with this product. But I haven't touched in for quite a while, so I wouldn't know. I don't remember the configuration, but I didn't feel a breeze like in Nginx. I have Nginx running for *months* with pretty much static memory consumption... also, the super-cool feature I like about Nginx is that you can upgrade it's version _without downtime_ i.e. no client is ever refused a request. It does so in a quite intelligent way, by loading the new server by the old one, and transferring the connections from the old one to the new one. > For now I see that I'll need https, mod_python, password protected > directories. > > HTTPs CHECK, mod_python, no, mod_* is an Apache thing. In Nginx, the web server does web serving, and the application server (WSGI which I mentioned before), runs the application. Every software does what it does best, which is, IMHO, the Proven Unix Way (TM). Web server connects to backend app server via a well-known protocol, like WSGI or FastCGI, over TCP/IP (so you can separate web serving from App server, and scale up easily), or Unix Socket (if running locally on the same machine...) > Got your point about non-standard http ports Let's stick to to the > standard. > > :-) > Valery > -- Shimi
_______________________________________________ Linux-il mailing list Linux-il@cs.huji.ac.il http://mailman.cs.huji.ac.il/mailman/listinfo/linux-il
