Deriving Typeable for ConnectionPool data family

Seems that for deriving Typeable for data families has to be done using
standalone deriving. Simply stating "deriving Typeable" yields syntax
error.
Switching from pathLens to getPath

Using pathLens required us to define function (^.) which is infix form
of get. By making this switch we simplified some code and reduced
imports.
Reexporting ClientSettings{,Unix}, AppData{,Unix}

It is quite annoying when GHCi shows types with qualified types when one
expects that all of it is in scope already. User still needs to import
things from "Data.Streaming.Network" (streaming-commons package) to use
this package sensibly.