Messages in this thread | | | Date | Mon, 21 Jun 1999 01:13:06 +0200 (MET DST) | From | Bjorn Wesen <> | Subject | Re: Why khttpd is a bad idea |
| |
On Sun, 20 Jun 1999, Dan Hollis wrote: [talk about embedded linux systems and webservers]
> A very, very, very minimal userspace web server that does CGI and nothing > else.
> in-kernel khttpd will likely be smaller than userspace one since > kernelspace one doesnt need libc and other overhead.
If you need at least one user-level program in an embedded device (like the "minimal userspace webserver that does CGI" above), you pull in some libc functions. But then you already have the libc functions, and the additional code for serving static web pages is trivial and doesn't add to the size noticeably.
Putting stuff inside the kernel is not the solution in that case. Using a lightweight c library is.
Granted, if the sole application of the embedded box is to serve some static webpages, and you don't need any other programs _at all_, then you can add the 150 lines of code in the kernel it takes to serve webpages (in a simple, not heavyweight-optimised manner). But then we're talking about a pretty specialised scenario.
/Bjorn
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.rutgers.edu Please read the FAQ at http://www.tux.org/lkml/
| |