Only check for IO Condition before trying another read when the socket is blocking [#23] In commit 79deb183d we added a check to see if there was more data to be read before trying again. This to avoid having a blocking socket hang on that call until some data became available. However, when using OpenSSL it sometimes reads everything off the TCP socket and buffers it internally which means that the TCP socket will tell us that there is no more data available which leads to us not trying to read from the OpenSSL layer again. In this commit I added a check to see if the socket was blocking before doing this. The long term fix will be that the socket is always going to be in async mode and the synchronous APIs will be handled at a higher level. [#23 responsible:Hallski milestone:Loudmouth 1.4.3 state:resolved]

Removed lm-soup-socket.[ch] These unused files was a test to implement the new network backend using the SoupSocket from libsoup. However, I'm not inclined to add libsoup as a dependency to Loudmouth so they will not be used.

Make the new libasyncns compile on mac os x

Updated asyncns.[ch]

Added some verbose debug output

Improved the resolvers a bit. LmOldSocket currently creates a new resolver when doing a host lookup after a successful srv lookup.

Removed optional definition of _lm_sock_set_keepalive. Always define the method but make the implementation noop if TCP keep alives are not available.

Removed the async_connect_waiting and blocking states from LmConnection. As a first step of cleaning up the network code underlying LmConnection I want to make the blocking and non-blocking calls be as similar as possible. The socket should be able to connect in asynchronous manner even if we want to block on the open call since the mainloop iteration will handle the "block" for lm_connection_open_and_block.

Minor style fix

Removed unused variable in lm_connection_open_and_block