Review and refactor the internals of Grocer::Server, Grocer::SSLServer

[alindeman]

We've run into weird issues, especially on different platforms (e.g., Linux vs. OS X) dealing with setting up and tearing down a Grocer.server.

This issue is to audit the code that's currently written, looking for ways to improve the ways the server socket is setup and used. We should consider stuff like whether using non-blocking/async calls is more appropriate, and how to make sure that all platforms react well to the changes.

[stevenharman]

I wonder if we need some integration tests to test our integration test server.

[alindeman]

Probably! Good idea.

[kyledrake]

You may want to investigate read_nonblock and write_nonblock, and putting things in threads (ruby does not block on IO when threads are used despite popular belief, it goes and works on another thread while waiting).