Comments on: The rise of lighttpd. http://pinderkent.blogsavy.com/archives/68 Just another Blogsavy.com weblog Sat, 11 Oct 2008 05:38:15 +0000 http://wordpress.org/?v=2.5 By: Me. http://pinderkent.blogsavy.com/archives/68#comment-85 Me. Sun, 22 Jul 2007 23:34:52 +0000 http://pinderkent.blogsavy.com/archives/79#comment-85 Cherokee, which offers a similar featureset to lighttpd, is significantly smaller and cleaner. I'm not quite sure why anyone uses lighttpd, but I could see making an argument for Cherokee. Cherokee, which offers a similar featureset to lighttpd, is significantly smaller and cleaner. I’m not quite sure why anyone uses lighttpd, but I could see making an argument for Cherokee.

]]> By: ynw http://pinderkent.blogsavy.com/archives/68#comment-84 ynw Sat, 21 Jul 2007 15:05:35 +0000 http://pinderkent.blogsavy.com/archives/79#comment-84 I would suggest to consider Nginx (http://wiki.codemongers.com/Nginx) as a more reliable solution. lighttpd disappointed many users (myself included) with memory leakage and other strange behaviours. Nginx has prooved to be stable, reliable and to be ready to handle large amount of traffic. I would suggest to consider Nginx (http://wiki.codemongers.com/Nginx) as a more reliable solution.

lighttpd disappointed many users (myself included) with memory leakage and other strange behaviours.

Nginx has prooved to be stable, reliable and to be ready to handle large amount of traffic.

]]> By: backdraft » Blog Archive » The rise of lighttpd http://pinderkent.blogsavy.com/archives/68#comment-83 backdraft » Blog Archive » The rise of lighttpd Sat, 21 Jul 2007 14:33:10 +0000 http://pinderkent.blogsavy.com/archives/79#comment-83 [...] minipost 456 : The rise of lighttpd [...] […] minipost 456 : The rise of lighttpd […]

]]>