> Date: Mon, 26 Nov 2001 13:59:22 -0800 > From: George Pajari <[EMAIL PROTECTED]>
> Don't get me wrong - we really like mathopd. If you need > cgi-bin, security, virtual servers, etc. and etc. then mathopd > is great. But you don't so go with something smaller and > simpler. Agreed to a certain extent. It sounds like the OP will be rolling up his sleeves and coding a bit, anyway... so perhaps micro_httpd would be a good start, but perhaps mathopd would be better. (IIRC, micro_httpd was inetd-only, which is a bit of a drawback.) Mathopd has such nice, clean architecture that one can easily strip unwanted functionality. I think that I removed CGI and authentication before I even compiled and ran it the first time. I'd start with something that works together, then rip out the extras, as opposed to adding on to something simpler. If fewer config knobs are needed, simply reduce the config routines appropriately. Mathop source is clean and friendly, and you're that much farther down the HTTP Of course, one must also consider license issues for an embedded system. I'd have to check both httpds' licenses before making any recommendations on those grounds. Also IMHO. Eddy --------------------------------------------------------------------------- Brotsman & Dreger, Inc. - EverQuick Internet Division Phone: +1 (316) 794-8922 Wichita/(Inter)national Phone: +1 (785) 865-5885 Lawrence ---------------------------------------------------------------------------
