thttpd, patches, thanks and caveats


1. Thanks

I really want to thank people who posted patches to thttpd mail archives or argued about some of the patches I put together in order to be applied in one shot, without clashes.

I also want to thank the author of thttpd for not having blamed too much my random development patches.

2. Explanations

My patches, focused on file cache performances (static only contents), have also other interesting, yet experimental, new features / improvements that, someday, after further tests and refinements, might be included into official versions of thttpd (at least I hope so).

Usually, I try to submit a few patches to thttpd mailing list or to the author of thttpd, soon after every thttpd official release; IMHO this is the most effective way to contribute new features.

RULE: the more often official versions are released the more often I am willing to submit contributes.

In conclusion, there is no competition with official thttpd releases; my patches should be seen as a small complementary effort to help thttpd development cycle (which is a bit slow because of lack of time).

3. Caveats

Please, before trying to apply a patch, be sure to read / know these instructions about how to apply a patch of mine to thttpd.

NOTE

Usually each patch includes all previous (older) ones (i.e. patches have not to be applied incrementally).

DISCLAIMER

My patches are provided as free contributions to thttpd software, without any express or implied warranty they work well or fit any particular purpose (see also standard disclaimer in thttpd sources).

WARNING

Test development patches at your own risk and take note that they apply to old thttpd versions.

Last Updated: 06-JUN-2003