While reading through the connection pool code, moved it from
extending a prototype object in an interator to just doing
Pool.prototype.foo =, mostly because that's how the rest of the
code does it.

The pool now emits a couple of log events when hosts enter the dead
list. Will extend this logging further in a moment.
Dry-coded connection monitoring using a query of the system keyspace.
Enable connection monitoring and more log events.

Every ten seconds, we do a query of the system keyspaces for all
clients we expect to be alive. If they're not alive (timeout, error),
they go in the dead pool, which we periodically check as well.
We also set their ready flag to false, so we do not attempt to use
those connections in the pool.

We *did* have a way to notice dead nodes at startup, but there was
nothing that noticed dying nodes to take them out of the pool. Now
there is.
Bump version.
Bump monitor timer to 15s to match other services.
Merge pull request #2 from blackpearlsystems/pooling-two

Add connection monitoring