List of things it need:
* HTTP 1.1
* 200 OK
* 404 Not Found
* Built-in 404 page [or user selectable]
* Some sort of _built-in_ scripting (ex. lua)
* Must be able to tell MIME type from file extension or contents
* Less than 1000 lines total (needs to be READABLE!)
* Doesn't use boost (fgts) or std (fgts). CRT is OK.
* Must be CONFIGURABLE [via command line or file]
* Only use standard sockets no SFML/boost/other [ie: winsock]
* Can be multi-client or be multi-threaded
>>9
I find >>5 to be quite nice, it's configurable and scriptable, however I can see where you're coming from. Non-portable code tends to fill me with disgust. Since my main platform is Win32 (I use some flavours of *nix too), it's readable to me, however I tend to find completly unportable *nix code (which uses non-POSIX interfaces or whatever the OS offers) to be just as disgusting, so I can see where you're coming from. It's a shame portability in some languages is a lot more painful than in others, and most platforms I've encountered so far encourage the user to write non-portable code, some moreso than the other.
>>1 I wrote a small HTTP server, what will I do with it? Oh, I know, I'll start a shitty "contest" thread on /prog/ so that I can post it and win because no-one else will give a shit.
ftfy