Return-Path: X-Original-To: apmail-curator-dev-archive@minotaur.apache.org Delivered-To: apmail-curator-dev-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id C236A183D8 for ; Thu, 10 Mar 2016 22:11:26 +0000 (UTC) Received: (qmail 58610 invoked by uid 500); 10 Mar 2016 22:11:26 -0000 Delivered-To: apmail-curator-dev-archive@curator.apache.org Received: (qmail 58569 invoked by uid 500); 10 Mar 2016 22:11:26 -0000 Mailing-List: contact dev-help@curator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@curator.apache.org Delivered-To: mailing list dev@curator.apache.org Received: (qmail 58558 invoked by uid 99); 10 Mar 2016 22:11:26 -0000 Received: from git1-us-west.apache.org (HELO git1-us-west.apache.org) (140.211.11.23) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 10 Mar 2016 22:11:26 +0000 Received: by git1-us-west.apache.org (ASF Mail Server at git1-us-west.apache.org, from userid 33) id 3C587DFBDB; Thu, 10 Mar 2016 22:11:26 +0000 (UTC) From: Randgalt To: dev@curator.apache.org Reply-To: dev@curator.apache.org References: In-Reply-To: Subject: [GitHub] curator pull request: [CURATOR-306] Background operations would be... Content-Type: text/plain Message-Id: <20160310221126.3C587DFBDB@git1-us-west.apache.org> Date: Thu, 10 Mar 2016 22:11:26 +0000 (UTC) Github user Randgalt commented on the pull request: https://github.com/apache/curator/pull/139#issuecomment-195074289 Yeah - I agree. Maybe we can start a discussion on Curator 4.0 and open it up to major refactoring. --- 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. ---