marking a method with IOThread
making sure the output jar has the right name
my silly math meant on single core machines there were no threads to do
i/o processing, which caused a fun pause in the festivities during the
test deployment into aws. luckily my first instinct was to debug because
otherwise i would have still been trying to figure out wtf
just adding some quick monitoring to at least log if there are tasks not
executing at all.  not even sure if it works yet but i have a lot of
things in flight and i wanted to scratch down the idea
logging that configuration has been found during startup to increase
confidence in correct initialization
netty upgrade necessitated some changes in response handling, no more
FullHttpResponse, content is now managed individually.  not doing
transfers ATM but soon.  can also test compression out again, and make
it configurable?

perhaps soon make the net system restartable? that'll be trickier.
there will be long-term connections
ensure we exit with an error code if there is an error that causes us to
exit.  also, added a quick console listener for a stop command, which
right now is ctrl-c directly (char code 3) and not just as a signal, so
the gradle build can start/stop the server.  hacktastic!
added a class to manage a full JibbrJabbr server inside the build
okay, let's have tests against a full running server. and let's see how
travis likes it