はてなブックマーク

Some time ago we got a request on how to implement COMET with lighttpd. I responded with a idea about a mod_multiplex which would allow the let the client open a COMET-channel and give the backend the possibility to feed multiple channels at once with the client to poll for new data. Basicly it would separate the HTTP Request-Response cycle from the underlying connection. HTTP would be used to ope

The benchmarks only showed results for small files (100kbyte). Time to add larger files to the pool and talk about the chunk-size. I just push all the work to the kernel and hope that it does it right. Currently I allow 64 jobs to be pushed to the kernel. Kernel threads are more light-weight that “real” threads. Currently I’m working on a posix AIO version. On linux that is using threads to handle

Yeah, really. Before you jump around and empty a barrel of beer, try to compile it first. :) Download: www.lighttpd.net/download/lighttpd-1.5.0-r1435.tar.gz Finally I got some time to finish the loose ends of 1.5.0. MySQL Network MAS is going to release (hopefully) next week, giving me time to work on lighty again. What works and what doesn’t ? mod_fastcgi, mod_cgi, mod_scgi, mod_proxy are removed

trunk/ just got support Linux Native AIO. I implemented Async IO based on libaio which is a minimal wrapper around the aio-syscalls for the 2.6.x kernels. Implementation It was a bit tricky to get it working as libaio is basicly undocumented, but hey … that’s why we are hackers :) The async file IO support is part of Linux 2.6.9 and later and should be on every recent linux box. A separate library

... or the hidden secrets of lighty. X-Sendfile is one of the important, but mostly unknown features. Time to put the spot-light on it and see why you want to use it. X-Sendfile is a special header option you can set in any FastCGI backend to tell lighty to ignore the content of the response and replace it by the file that is specified in the X-Sendfile header. Doesn't sound dramatic in the first

I've just finished my presentation on lighty at the "railsconf":http://railsconf.org/ in Chicago, IL, USA. The slides of the presentation "Accelerating Rails with Lighty" have been uploaded to "www.lighttpd.net/railsconf-2006.pdf"://www.lighttpd.net/railsconf-2006.pdf Please note that we won't accept comments for posts older than 3 months! Also please use our bug tracker to report bugs, and our ir

I was always jealous of iruby and ipython, the interactive shells for Ruby and Python. Instead of writing a script and running it through the interpreters you just execute the script line-by-line while you write it. For debugging this is great. Compare a shell-script against the normal shell usage. It is more a ‘What if I …’ pattern instead of ‘I can write 100 lines of code without testing it’. PH

lighttpd 1.4.8 was just released and next to a pile of bugfixes we added a new option to fastcgi.server to allow a simple setup of multiple rails app in one virtual host. Next to the usual setup with fastcgi.server the new option ‘strip-request-uri’ removes parts of the request-uri before they are sent to the backend: $HTTP["url"] =~ "^/app1/" { server.document-root = "/home/jan/rails/app1/public/