Description
During the effort to resolve bugs related to the Vulcan release, a small code-smell was introduced which caused the semantics of memdConn to get muddled. Ideally the closed handling would occur at a higher level (memdClient) than memdConn as memdConn is essentially just a TCP connection wrapper. See the comments in this review for more details: http://review.couchbase.org/#/c/95973/.