Perform server communication in a separate thread

Currently server communication is performed in the main thread. This involves speaking checking sockets, copying data, parsing data into Atlas structures and then handling those Atlas structures in Eris.
While we don't want to make the whole of Eris thread safe, we would want to separate all of the stages up to where the Atlas data is handled by Eris, so that these actions can occur in a background thread. This would mean that Eris would become less self contained and more of the responsibility for handling the low level operations would be delegated to the application. Or at least the initiation of these actions.