Lighttpd again
New stuff will be posted at cleanpixels.blogspot.com. I have built a new lighttpd for win32 base on /trunk:2001, as well as produced a patch that makes it easy to build from source.

 

Lighttpd update

Jani Tiainen did a stack of work finishing up where I left off on lighttpd on win32. This is really just a preview build of the latest source, it's pretty rough. There's no ssl, mod_magnet, or mod_deflate.

Download /trunk:1700 (1 March 2007)

 

Lighttpd 1.5.0 native on Win32

After some blood and sweat, but hardly any coding, I've managed to get lighttpd to run decently (for my purposes) on Windows. I wouldn't recommend you go try run Youtube on this, but it's useful if you use lighty on your real servers, but like to code in Windows. I will submit the source patch soon, once I'm a little more confident it's all sane. Jan got lighty working on win32 a couple months ago, but nobody has since bothered to maintain it. If I end up with enough time, and nobody does it better, I'm taking up the job.

What's in the package?

  • A REAL native win32 build of lighty. The total code base, including all modules, is 2MB, the way it should be.
  • All the modules included in the 1.5.0 trunk, except for webdav, rrdtool and cml.
  • mod_proxy_core works, but x-sendfile does not.
  • I haven't tried the FastCGI backend, but I can confirm that the SCGI backend works. I have yet to write a proper spawn-fcgi for Windows. If you're doing rails or the like, I'd recommend SCGI for now.
  • Some quick tests reveal static file serving at about 2x the number of connections per second as Apache 2 on Windows.
  • Most other modules work, but are not thoroughly tested.

Download Installer (1.3MB)
(note: you may have to install the MSVC8 CRT, which is included in the package. Instructions in the readme.)

Caveat:
The only command line option allowed is -f path/to/lighttpd.conf. This is hardcoded/hacked in.

This entire package is provided as-is; no guarantees as to security or reliability.

If you have any questions, you can email me at my gmail address, which is evident from this page.

 

 

Logitech G5 is not an upgrade on the MX518.

I posses a fair number of mice, including an MX300, an MX500, an MX510, an MX518, an MX1000, a slew of Microsoft mice, and of course a G5.

Minutes after plugging in my G5, my wrist began to pain. I couldn't bear the thought that my 2000 DPI laser mouse might be at fault, so I changed my acceleration settings, messed with the weights, flashed the firmware, used the exact same mouse, exact same config, at home as at work. After three months I eventually conquered the buyer's remorse, and admitted the rodent was a downgrade from my MX518.

I think the problem lies in the texture of the G5, the 'metallic' portion as well as the rubbery side bits. I use primarily the palm of my hand to move the mouse. The friction I receive against my palm on the G5 is far less than I get on the surface of the MX518. Try picking the mouse up by gripping it between your palm and your thumb.

This awesome review (if you're into mice) also brings to light the fact that the laser sensor is probably not as great as it's made out to be.

How does a company like Logitech make such a blunder? You tell me.