Just a few minutes ago lighttpd 1.4.1 has been released, shortly after lighttpd 1.4.0 which had some user-visible problems.
1.4.1 fixes those bugs, stabilizes the SSL support on OpenBSD and
finishes the WebDAV support in mod_webdav to Class 1 (all options except
LOCK/UNLOCK).
Xuefer pointed me to a thread on internals mailinglist on php.net. It starts nicely with the question if a upgrade to Apache 2.x can solve the low-latency problem that arise when you want to use AJAX on a high-traffic site, talks about keep-alive and its problems until Andreas Korthus throws lighttpd into the game.
1.3.15 is like a best-of album from your favourite band which contains all the good song, a few remixes and one or two new songs, just to make sure that you buy it.
We did the same: the core stuff got bugfixes and two new modules were added which might interest you:
mod_cmlMove the cache-hit decision into the webserver and only call the external language on cache-miss to speed up dynamic apps dramaticly -> cluster-enabled via memcache
mod_trigger_b4_dlFor our content-providers which require that the user visitsa URL before he is allowed to download the content -> cluster-enabled via memcache
mod_cmlmod_trigger_b4_dlmod_dirlisting?auto to mod_statussendfile() on Linux 2.4.xserver.errorfile-prefix is now conditionalmod_rrdtool to close STDERRAfter the logo-contest went very well and we have seen very nice and professional proposals lighty finally has a logo.
The winning entry is based on the paper airplane submitted by Phu from endturn. It was modified by Paul from openartist.net.
Good work. Now we have a nice button which everyone can add to their sites and link back to https://www.lighttpd.net/.
For a real big one, we have the big logo with a nice slogan:
For more information about the idea of the logo and more background on how lighttpd was started check the story of lighttpd on lighttpd.net.
Xuefer opened a ticket to document the history of lighty.
As we have a new logo now I wrote everything up, why I started it, why I continued and were we will head to.
If you want, add your date when you started using lighty to the comments.
After the release didn’t reveale any serious bugs the documentation was updated and the final release was roled.
Get it at https://download.lighttpd.net/lighttpd/ and spread the word.
I would like to see some comments on the loadbalancers in mod_proxy and
the new mod_scgi.
The last release of lighttpd is now 3 month ago and several patches are waiting for their release.
Next to several bug-fixes it contains a simplified
CARP
(Cache Array Routing Protocol) like load balancing for mod_proxy and a
new mod_scgi
for WSGI +
python.
The first public pre-release has been upload and is meant for a wider testing than the svn-tree.
Please don’t put that on a production system yet even it contains mostly bugfixes.
After poking I was poked several times to publish a benchmark between lighttpd and Apache2 I added it to the benchmark page.
More impressive than scientific benchmarks are real-world tests like the oen Jason has done: Taking a full frontal slashdot lighttpdly at textdrive. :)
Yeaha, what a impressive contest. So many nice ideas on how to interpret the word light. Even in the last days before the contest was closed we got some final submissions. I’m impressed and confused in the same way.
I can’t draw a decision on my own. I need your help. Think about the following questions and post yours answers in the comment.
I have some personal candidates, but can’t come to a final conclusion, perhaps you can help me ?
Only 7 days are left for the lighttpd logo contest. In the last week 3 artists have sent in there submissions with one of them being so creative to submit 8 logos at once.
Please take a look at the new submissions and leave your comment under this article.