<div dir="ltr"><br><br><div class="gmail_quote">On Sun, Sep 25, 2011 at 1:28 PM, Valery Reznic <span dir="ltr"><<a href="mailto:valery_reznic@yahoo.com">valery_reznic@yahoo.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div><div style="color:#000;background-color:#fff;font-family:times new roman, new york, times, serif;font-size:12pt"><div>I am tempted to try :)<br><span></span></div><div><span><br></span></div><div><span>What do you think is better Nginx or lighttpd?</span></div>
</div></div></blockquote><div><br>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.<br>
<br></div><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;"><div><div style="color: rgb(0, 0, 0); background-color: rgb(255, 255, 255); font-family: times new roman,new york,times,serif; font-size: 12pt;">
<div><span>For now I see that I'll need https, mod_python, password protected directories.</span></div><div><br></div></div></div></blockquote><div><br>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...)<br>
<br></div><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;"><div><div style="color: rgb(0, 0, 0); background-color: rgb(255, 255, 255); font-family: times new roman,new york,times,serif; font-size: 12pt;">
<div><span></span></div><div><span></span>
</div>
<div><span>Got your point about </span><span>non-standard http ports Let's stick to to the standard.</span></div><div><br></div></div></div></blockquote><div>:-)<br> <br></div><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<div><div style="color: rgb(0, 0, 0); background-color: rgb(255, 255, 255); font-family: times new roman,new york,times,serif; font-size: 12pt;"><div><span></span></div><div><span>Valery</span><br></div></div></div></blockquote>
<div><br>-- Shimi <br></div></div></div>