Mailing-List: contact dev-help@curator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@curator.apache.org
From: madrob <git@git.apache.org>
To: dev@curator.apache.org
Reply-To: dev@curator.apache.org
References: <git-pr-39-curator@git.apache.org>
In-Reply-To: <git-pr-39-curator@git.apache.org>
Subject: [GitHub] curator pull request: CURATOR-136 Make LeaderLatch handling
 of rel...
Content-Type: text/plain
Message-Id: <20140820154629.9B41595496B@tyr.zones.apache.org>
Date: Wed, 20 Aug 2014 15:46:29 +0000 (UTC)

Github user madrob commented on the pull request:

    https://github.com/apache/curator/pull/39#issuecomment-52797577
  
    I looked through them and didn't see any that wouldn't fail fast due to delegated checks in the constructors. Very possible that I missed some, though.
    
    Were you thinking that you want an explicit check in each recipe instead of relying on the underlying client behavior?


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastructure@apache.org or file a JIRA ticket
with INFRA.
---