Return-Path: X-Original-To: apmail-zookeeper-user-archive@www.apache.org Delivered-To: apmail-zookeeper-user-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 532209FDE for ; Wed, 14 Mar 2012 06:05:32 +0000 (UTC) Received: (qmail 15526 invoked by uid 500); 14 Mar 2012 06:05:31 -0000 Delivered-To: apmail-zookeeper-user-archive@zookeeper.apache.org Received: (qmail 15288 invoked by uid 500); 14 Mar 2012 06:05:28 -0000 Mailing-List: contact user-help@zookeeper.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: user@zookeeper.apache.org Delivered-To: mailing list user@zookeeper.apache.org Received: (qmail 15257 invoked by uid 99); 14 Mar 2012 06:05:27 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 14 Mar 2012 06:05:27 +0000 X-ASF-Spam-Status: No, hits=1.5 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of manosizb@gmail.com designates 209.85.213.170 as permitted sender) Received: from [209.85.213.170] (HELO mail-yx0-f170.google.com) (209.85.213.170) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 14 Mar 2012 06:05:21 +0000 Received: by yenl5 with SMTP id l5so1432909yen.15 for ; Tue, 13 Mar 2012 23:05:00 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:content-type; bh=1EOAMRW3TabRI1NyzNC/tK3jf1zLrtnm7wj183AnKTk=; b=HmGdlQSeV1hA6LIojf6YdAKkAT1ZX1erevE9xYjRaVZqYJLP9EATROZPrBx8IM1shV djXEAQIKLs9j5Y69ixyXQ5zJ2oBCGN90u+VfGj2GEmKS64xukSyBtEVjJh4cBYUJIvSZ WuZp5AqFTEsuMFEG+AseTXFn9HMllwCQYueO0JPTz652tv27+e3k2qKvT2uhs/sL0Avb uFzKFv70Oqz2eVwDl9z+DOno2/6cfud2OKlgdg/zaMqsnUTzRQ0wS+758u0hilqz8g/Z hmOu5+PUE0sTqT5Gtt1qGULpyQLMnD7dlPbf6tkq3TDnSbQWJmBFk7H6+o93arUT4sI/ 82Gw== MIME-Version: 1.0 Received: by 10.60.3.99 with SMTP id b3mr1232852oeb.72.1331705100544; Tue, 13 Mar 2012 23:05:00 -0700 (PDT) Received: by 10.60.63.193 with HTTP; Tue, 13 Mar 2012 23:05:00 -0700 (PDT) Date: Tue, 13 Mar 2012 23:05:00 -0700 Message-ID: Subject: State of the Zookeeper watch context on an ZCONNECTIONLOSS/ZOPERATIONTIMEOUT From: Manosiz Bhattacharyya To: user@zookeeper.apache.org Content-Type: multipart/alternative; boundary=e89a8f503c5876a88704bb2dc12f X-Virus-Checked: Checked by ClamAV on apache.org --e89a8f503c5876a88704bb2dc12f Content-Type: text/plain; charset=ISO-8859-1 I would like to know the state of the user context when a watch setting zookeeper API like zoo_awget() returns a ZCONNECTIONLOSS or ZOPERATIONTIMEOUT in the C async API's. Can the context be safely deleted at this point, and can we be sure that a watch will not be fired with a dangling pointer. Thanks, Manosiz. --e89a8f503c5876a88704bb2dc12f--