Attempt re-connection immediately when notified of a broken connection
Start the tick again, in case we need it
Merge pull request #74 from bboreham/28_retry_faster

Attempt re-connection immediately when notified of a broken connection

Fixes #28
Only push two tags - latest and git-commit - to DockerHub
Updated to reflect version-tagging process
Merge remote-tracking branch 'upstream/master' into HEAD
Merge pull request #76 from bboreham/tag_fix

Only push latest and git commit tag to DockerHub
cosmetic
cosmetic - remove comment for which we have an issue filed
refactor: we don't care about the tick time
refactor: use better 'switch'
eliminate periodic 'tick' in connection_maker
checkStateAndAttemptConnections already performs a full scan of all
potential targets, from which we can easily determine the nearest
future time (or, rather, its duration from now) on which an attempt is
due.

We also need to kick the ConnectionMaker into action when we receive a
topology update containing new connections.
Merge pull request #78 from zettio/77_eliminate_connection_maker_tick

eliminate periodic 'tick' in connection_maker
don't set pcap timeout, to prevent cpu churn
pcap timeouts are a mystery. Setting the timeout to -1 used to reduce
latency, but that was before we started setting immediate mode. And it
turns out that with that timeout, pcap chews through a lot of CPU
polling its file descriptor, checking timers, etc.

With no timeout set an idle weave is completely idle - no system calls
at all.

Fixes #80