Mailing-List: contact zookeeper-user-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: zookeeper-user@hadoop.apache.org
Received-SPF: pass (nike.apache.org: domain of maarten@vrijheid.net designates
 69.64.155.202 as permitted sender)
Message-ID: <4B0AC34E.9020907@vrijheid.net>
Date: Mon, 23 Nov 2009 18:15:58 +0100
From: Maarten Koopmans <maarten@vrijheid.net>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; nl;
 rv:1.9.1.4) Gecko/20091017 SeaMonkey/2.0
MIME-Version: 1.0
To: zookeeper-user@hadoop.apache.org
Subject: legacy style watchers - or none at all
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

Hi,

I am coding away on yet another client interface, and I can live in a 
situation where I have no watchers. Callbacks into my interpreter are a 
bit risky as well, so I am opting for the legacy style now, wrapping the 
c interface in such a way that it never allows watchers on paths (and 
hence, callbacks).

My question is: "legacy style" watchers... legacy implies they'll go? I 
hope not, or if so, we can get the C watcherless (I am not sure how the 
C API would handle a void (empty char*) pointer for a callback). I like 
being able to set the boolean to false for legacy style watchers - it 
saves me a lot of trouble.

--Maarten