would folks be interested in an "implement a toy version of HTTP/1.1 in a weekend” guide? I'm imagining something super basic (~100 lines of Python, not remotely standards compliant), just a server that opens a TCP socket, takes HTTP requests, and returns responses.

@b0rk Heh, I wrote the worst “server” imaginable in portable shell printf & netcat as an integration test subject for HTTP nagios plug-ins years ago.

I expect to be amazed with what ~100 lines of clear python can deliver.

@josephholsten It’s kind of amazing how simple a lot of these technologies fundamentally are when you dig in. Writing an HTTP server in C back in college was a revelation at how little there actually is at the core.
@alpha A webmachine level of protocol correctness, with efficient file system access, caching and C10k concurrency: a deeply challenging project.
A derpy 200 OK loop on a socket: a delightful example of why 4.3BSD TCP/IP socket API won