I'm very much in favor of having a standard Busybox/uclibc-based distribution available on the empeg. However, which "more complete" web server would we be talking about? More complete suggests more resource-hungry. Aside from CGI support, what else do we need from an empeg web server that we don't get already from khttpd? I would prefer not to have extra resources taken up to get the same webserver functionality we have right now, and I'm not familiar with any "lightweight" httpds out there that would give us anything like what we get from khttpd, without significant modifications.

If you do decide to go this direction, can you keep khttpd around, optionally compiled in for those of us who would like to stick with it?
_________________________
- Tony C
my empeg stuff