yahns and unicorns are complete opposites in terms of design. Unfortunately, comparisons between yahns and unicorn may be inevitable since they are implemented and maintained by the same BDFL, and even share the common HTTP parser and some code.
unicorn was only introduced in 2009, with a design which would have been considered obsolete in 1999. But even in 2015, implementations (even non-Ruby ones) based on one-shot epoll/kqueue notifications like yahns are barely used and can probably be counted on one hand. Overview of differences: * blocking vs non-blocking accept (yahns does the former(!)) * blocking vs non-blocking read/write * "timeout" configurator directive can only be supported in unicorn * slow vs fast client handling * thread-safety, async-signal safety More to come... -- unsubscribe: yahns-public+unsubscr...@yhbt.net archive: http://yhbt.net/yahns-public/
