Meanwhile... 12

Posted by icy Sat, 12 Sep 2009 17:45:00 GMT

Hey folks,

back in december, we posted about a new lighty branch and opened up our project to the public: http://redmine.lighttpd.net/wiki/lighttpd-sandbox

It’s still not in a fully useable state yet, but we have been very busy and made huge progress meanwhile. Look what we had last time:

Dec 08:
  • the config handling is pretty complete
  • basic connection handling including throttling and keep-alive/IO timeouts works
  • error logging works (introducing multiple error log levels and targets)
  • module/plugin interface mostly done
  • completely multithreaded
  • serves static files

Apart from some minor features we can now say the core is almost done with just small changes or optimizations to it. We now start to add functionality to the core via modules and following ones already work pretty well:

  • mod_accesslog
  • mod_auth (auth-basic with plaintext files working)
  • mod_dirlist
  • mod_expire
  • mod_fastcgi (working pretty well already, giving usability a big boost!)
  • mod_openssl (ssl functionality provided through openssl)
  • mod_redirect (more powerful than in 1.x)
  • mod_rewrite (also more powerful than in 1.x)
  • mod_status
  • mod_vhost (virtual hosts, plenty of options and possibilities; combines mod_simple_vhost and mod_evhost plus more)

Performance seems to be really great so far. Thanks to being fully multithreaded, lighty 2.0 scales nicely with multicore CPUs.
It can handle several hundred thousand requests per second on a new Intel i7 (for really small static files, on localhost, not a great benchmark :P).

Let me tell you, alot has changed! And of course you’re welcome to test and have a look at its current state. But – just like last time – the forum as well as ticket/issue tracking is still disabled for it because we are not capable of providing any support as well as getting things done within a reasonable amount of time – so we focus on getting things done. :)

Some people might already be able to do basic stuff like serving static files, maybe play with fastcgi a little. As the config and design completely differs from 1.x you might already want to take a look or “test ride”. Remember: No support at the moment. :-)

We can’t (and really don’t want to) provide any specific release date but hope to have 2.0 in a usable state by the end of the year. Remember we do this in our free time for fun.


As for lighty 1.4 and 1.5: everything will continue like before – no worries.

This is it for today.


Thanks for flying light.

Comments

Leave a response

  1. Josh Davis Sat, 12 Sep 2009 18:39:02 GMT
    Great news. Glad to see that 2.0 is progressing at a good pace ;)
  2. akrus Sun, 13 Sep 2009 12:16:37 GMT
    currently using on my home PC for serving several static files - works perfectly... and the new mod_status is so great! :)
  3. Diego Sana Tue, 15 Sep 2009 21:25:57 GMT
    Very nice. What about that mod_mailbox that's announced in the homepage in a post that's 3 years old. Is that going to make it into lighttpd?
  4. icy Wed, 16 Sep 2009 08:59:24 GMT
    Diego Sana: yes mod_mailbox/comet support amongst a lot of other stuff is planned. But there's only so much time we can put into it, and other things have higher priority so you'll have to wait until we get around doing it ;)
  5. crushmaster Fri, 18 Sep 2009 04:44:41 GMT
    Today is lighty testing day @ home. Bad weather, great software... And please don't hurry, good things take a while! ;)
  6. Tim Sat, 19 Sep 2009 03:30:48 GMT
    Long time ago, Lighttpd was king ... and then came along NGINX. I would like to see Lighttpd king again.
  7. Adrenalin from Moldova Mon, 21 Sep 2009 19:32:13 GMT
    Unfortunatly no big site use lighttpd(or maybe just youtube?and only for static files?), I think that's main problem. Nginx is used on a big russian site rambler.ru. Sad to say, but I think I'll migrate soon my latest lighttpd server because of very annoying bug.. Keep getting "curl: (18) transfer closed with outstanding read data remaining" and that seem to be the problem of other strange bugs.. Maybe that's because of mod_proxy, the page is not going directly.. If you have any suggestion how to debug that, maybe I'll try during weekend. I'm on 1.4.22, in the 4.23 "removed spawn-fcgi" and I'm too lazy since the server is in production ;] But again, maybe I'll try during the weeked
  8. Adrenalin from Moldova Mon, 21 Sep 2009 21:11:08 GMT
    server.protocol-http11 = "disable" ---------------------------------------- makes the bug go away, now go guess
  9. icy Tue, 22 Sep 2009 06:24:31 GMT
    Adrenalin:
    1. Why do you say no big sites using lighty? That's a lie. Some of the biggest sites on the internet use lighty and not only for static files but for the whole thing. We even have a list with some of them in the wiki (not hard to find).
    2. This is not a bugtracker and if you have a problem, then report it. How are we supposed to fix it otherwise? BTW: I have not seen similar reports to yours. And not updating because you are to lazy... well, maybe I'm too lazy to debug for you then? :)

    Keep in mind: we do this on a purely voluntary basis. If you don't pay us then the least thing you can do is putting some effort into helping fixing a possible bug.
  10. mal Thu, 01 Oct 2009 07:30:20 GMT
    good points icy on the previous post. Iam really happy to see a work is in progress. mod_mailbox or this supposed method as you mentioned in your post about mod_mailbox would be one of the features which would make things for RESTful applications like mine depending on lighty just awesome. I have a question depending on the plugin interface. My plugins to lighty depending on C++ and we did a lot of work to implement c++ ways to the plugin interface and get it compiling in windows. Will lighty 2.x make things easier in these particulary tasks, does lighty now have a "real" system abstraction layer for IO operations so platform developers could contribute better for bugfixes or mention bugs they discovered? i know this would be bloating code of lighty a bit, so i can understand if you dismissed the idea before. the lighty 1.5 is design now now is ok for me too. keep on flying lighter
  11. icy Thu, 01 Oct 2009 14:54:09 GMT
    mal: the plugin interface in 2.0 is simpler or better structured in my opinion.
    As for C++: we do not have any plans for an official C++ API but I think it shouldn't be too difficult to create one.
    We also don't have any abstraction layer for IO operations but we use POSIX so it should compile on windows. And as we now use glib and libev, those bring some portable wrappers that you can use.
    hazzadous from IRC has created a C++ plugin API for 1.x
    wiki page: http://redmine.lighttpd.net/projects/lighttpd/wiki/CppModules
    project page: http://code.google.com/p/lighttpd-cpp/
    No idea if you have seen that but may be useful to you.
  12. Tim Mon, 05 Oct 2009 14:43:46 GMT
    I believe Youtube early on was using Lighttpd but they had to rework so much of the code I don't believe it looks anything like lighttpd anymore.
Comments