title: What's the advantage of "one thread per connection" in an HTTP server?
body: <p>If I was programming an HTTP server, why should I consider handling every HTTP connection in its own thread?</p>
  
  <p>I've read plenty of arguments that event-driven HTTP servers are faster and more scalable than thread-driven ones. (For example, see Ars Technica on <a href="http://arstechnica.com/business/news/2011/11/a-faster-web-server-ripping-out-apache-for-nginx.ars" rel="nofollow">Nginx</a>). And yet Apache, the world's most popular server, is thread-driven. Why? What are the advantages?</p>