C# web server

1. listen and respond with a basic web page
2. serve html from a folder
   • does this handle pages with img tags?
   • customize 404 pages
   • customize 500 pages
3. command line options for the server
   • number of requests
   • port number
   • change folder we are serving
   • restrict files
   • max/mean times to process requests
   • most popular files
   • dynamically load a class???
4. factor out how to send an HTTP response
5. handle mime types with a Dictionary and a config file
   • csv or json?
6. handle all server config with properties or json file
   • probably json because it's more common
7. fake servlets
   • list data from a json file as HTML

Threads and clients

1. build a simple client to connect
2. build a client with a 10 second delay
   • show that this is very slow...
3. create a new thread for each request
4. build an evil client that creates dozens of requests
5. performance hit for creating new threads
   • spinning up/down a thread is not free
6. thread pool