TODO

Features:

Design questions / Ideas:
- Figure out where the logger configuration logic belongs in the Launcher/BehaviorServer relationship
- Should the default logger go to STDERR or STDOUT?
- Log every request to the server/behavior, in addition to open, close.  For this to work, it would have to be the
  behavior's responsibility, since GServer#serve gets called only once for the lifetime of the connection.
- If we extract a commong logger, we might use that to test for proper disconnection in NeverRespondTest#test_disconnects_after_client_closes_connection

Future Behaviors:
- Create a more configurable version of the DelugeResponse which allows for a header, footer, content and times to repeat.
- Write the remaining bad HTTP behaviors.  In addition, we may want to replace the NaiveHttpResponse with something
  from the standard Ruby library, so that there's less code in this project, and so we know that we're
  following the HTTP protocol.
- Have a tiny listen queue (queue size 0) and a connection never gets into the queue
- Have a giant listen queue (queue size max?) and only one thread processing -- times out in the listen queue
- Close the write part of the connection, but not the read
- Close the read part of the connection, but not the write