Closes #24, Closes #22 : huzzah!

I started working on fixing the one handler per server over one handler
per request yesterday. I don't remember how far I got, but it wasn't
working. I stopped fairly early (~4:00pm), and came back to it this
afternoon. So many problems. SO MANY!

Anyways, it works now, and I'm kinda willing to say better than before.
I haven't done any tests, I have no idea, but I want to say it's
better...

As for actual changes, you're going to need to look at the diff. But
hey, this solves one huge thing we've been talking about for a while,
and fixes something somewhat trivial that's kinda nice.
Renamed HTTPHandlerFactory to HTTPRouter.

Because now it really is a router, and not an handler factory...
Implemented what I talked about in #22 before.

Specifically,
https://github.com/dkuntz2/java-httpserver/issues/22#issuecomment-34534402.

There isn't a `{*param}` yet, and there probably won't be, but
everything else is implemented and working.

Specifically the guessing what a handle method wants. Which is pretty
neat. Or, at least that works in theory... (in this case, theory means
there's a test that creates a new handler based on
https://gist.github.com/dkuntz2/8876955, and it creates the stuff just
fine; theory also means after doing some minor changes to our demo it
works too).

More tests are needed, and hopefully it'll be easier to work with now
that the code actually compiles. It was a huge pain having to write all
the code without being able to compile and run it. At least some tests
helped out.
Confirmed working.

While it was only theoretically working before, it is now confirmed
working (at least for adding in an HTTPRequest on demand).
Fixes #18 . Also, more comments!
Made changes talked about.

Mostly renaming. Some additional changes to make things work (staticized
MethodWrapper.cleanPath, because it's so useful, and the HTTPHandler
could use it...). There were some odd redlines, which were caused by
there not being parens on some method calls.

Basically just fixing it as we talked about earlier: make sure
HTTPHandler's router is called `router` and not `handlerFactory`.
Merge pull request #27 from dkuntz2/fix-22-and-24

Fix #22 and fix #24.

This means that the server can theoretically handle multiple connections at the same time, and only creates one copy of each handler. More specific details can be found in the code, previous commits, and the issue tracker (specifically issues #22 and #24).