[pkg-lighttpd] lighttpd-dev package?

[Anthony L. Awtrey]

On 08/03/2012 05:43 PM, Olaf van der Spek wrote:
> What's wrong with Apache? And what kind of plugins are we talking
> about? Maybe there's a better way to achieve your goal.

Nothing specifically wrong, it's just a little heavy and memory
intensive for my needs now.

Not to get too deep into it, but I've migrated an Apache + mod_php5
application to python using wsgi and a lightweight web framework. I've
been very happy with lighttpd, and particularly with its X-Sendfile
capability to deliver large, static content without passing it through
the application layer. I've found I can duplicate that capability in
Apache, so that particular feature isn't an issue and I can run the same
code on both servers.

I am doing some modified vnc port forwarding using a websocket
implementation served as an Apache module. I have found some people
doing similar stuff using lighttpd, but I'd really prefer to use mine.
I've got some additional features that probably no one else will care
about or want to include in a general purpose websockets module. Right
now I compile the Apache module using apxs without being tied to
specific Apache releases.

I was hoping I could keep my websockets module general enough to support
both Apache and lighttpd so I could continue to test before making a
final decision. If I have to rebuild my custom plugin with each lighttpd
update, it makes this approach much less interesting to me. I can just
stick with Apache and deal with the overhead.

Hopefully this email makes sense to someone who is not me. Ha!

Tony