Only uses pool
Pool size logging
Error types to determine when a server is down
Init with consisten hashing
Glock Client to handle multiple glockServers

Glock Client will handle multipel glock servers, if one server drops
due to a connection error, the client will drop the server from its
consistent hashing list. And then recursively attempt to lock again.

All consistent hashing calls are already protected by a lock inside the
library so we don't need to do any mutex locking while using them.
Check endpoint status first before adding into the hash table
Merge pull request #9 from iron-io/feature-consistent-hashing

Glock client to handle multiple glock servers using consistent hashing
goroutine to check for down servers status every 5 seconds
Init with one connection in each pool and add more connections on demand
Merge pull request #11 from iron-io/feature-consistent-hashing

Goroutine to check for down servers and connect back to them
Better Loggin
3 hosts for tests
MGlock Client to handle multiple glockServers

Glock Client will handle multipel glock servers, if one server drops
due to a connection error, the client will drop the server from its
consistent hashing list. And then recursively attempt to lock again.
erge branch 'master' of https://github.com/iron-io/glock
initialising channel for every channel
Merge branch 'master' into feature-syslog
Optional config and debug line