Yes, please use the code from CVS. I should have been released it already.
It well could be a bug. ethereal dump would clarify that and help with
debugging.
I definitely see a trend that the model shttpd uses now (finite state
machine) is hard to utilize.
I am more and more keen towards threading model.
Subroutines are hacky and not portable. Threads are easy to program.
If a user callback is called once per request, and may block, it would
make life way more easier.
Should we branch off shttpd version 2, a threaded one? What about those
embedded guys without thread support?
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
shttpd-general mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/shttpd-general
